--- title: Ableton Extensions SDK Field Guide description: A practical starting point for building and using Ableton Live Extensions. updated: 2026-06-04 raw_url: /raw/ableton-extensions-guide.mdx official_docs: https://ableton.github.io/extensions-sdk/ official_extensions_page: https://www.ableton.com/en/live/extensions/ --- # Ableton Extensions SDK Field Guide This guide is built for people who want to try, understand, or build Ableton Extensions quickly. It combines the official public SDK information with practical setup notes, beta limitations, and early Extension patterns. If you are using Claude, Codex, Cursor, or another coding assistant, point it at the raw version of this guide: ```text https://extforlive.com/raw/ableton-extensions-guide.mdx ``` Getting Claude to read this page is probably enough for most projects. As an alternate starting point, you can also check out [Oli Larkin's Ableton Extension Claude Skill](https://github.com/olilarkin/ableton-extension-skills). ## One-Screen Summary - Extensions are JavaScript/TypeScript tools that run alongside Live and interact with a Live Set. - They are triggered from Live's right-click context menus, not from the Browser and not from keyboard shortcuts in the current beta. - Extensions are best for discrete, user-triggered tasks: analyze a Set, transform MIDI, reorganize clips, automate prep work, generate ideas, connect to services, or create one-shot workflows. - Extensions are not for real-time audio effects, real-time MIDI monitoring, instruments, synths, samplers, persistent background agents, or replacing Live's core UI. - To use a downloaded `.ablx` Extension, you need Live 12 Suite Beta 12.4.5 or later. You do not need the SDK unless you are developing. - To develop an Extension, you need the Ableton Extensions SDK and Node.js v24.16.0 LTS. ## Official Starting Points - Official SDK page: https://ableton.github.io/extensions-sdk/ - Official Extensions page and example gallery: https://www.ableton.com/en/live/extensions/ - Beta and SDK download entry point: https://ableton.centercode.com/ - SDK/documentation download item, beta login required: https://ableton.centercode.com/project/version/item.html?cap=ea2ce822bd02401dba446c068717bc68&arttypeid={25c94141-9dd5-48e7-8775-632dd5861fa6}&artid={BEE6D733-E750-443B-BD8F-6CD4519A6F21} ## What Extensions Are Ableton Extensions are optional add-on tools for Live Suite. They are built with the Ableton Extensions SDK using modern JavaScript and TypeScript. They run in a separate Extension Host process and can interact with parts of a Live Set such as tracks, clips, MIDI notes, devices, tempo, structure, and project files. Think of an Extension as a command: the user chooses something in Live, right-clicks, selects an Extension action, adjusts parameters in a modal UI if needed, and runs it. The Extension does its work, returns a result or applies changes, and then stops. Useful mental model: - Max for Live is for real-time devices, patching, audio/MIDI processing, instruments, and continuous behavior. - Extensions are for one-shot JavaScript tools that read, transform, create, reorganize, analyze, or export Set data. ## What Extensions Are Good For The strongest Extension ideas usually fit one of these patterns: - MIDI transforms: reharmonize notes, generate variations, detect keys, create voicings, humanize timing, build patterns. - Set analysis: inspect tracks, clips, structure, naming, tempo, routing assumptions, missing assets, or session organization. - Editing automation in the workflow sense: rename tracks, create tracks, duplicate or transform clips, clear ranges, organize stems, prep sessions. - Offline or file-based audio workflows: render or read supported audio resources, process files, write new files, and create clips from those files. - External service workflows: send selected material to a model, API, notation service, catalog, metadata tool, or asset manager. - Creative experiments: games, visualizers, strange generators, composition assistants, and tools that would be too weird to ship as core Live features. ## What Extensions Are Not For The current beta is not a replacement for every Live API, Max for Live, MIDI Remote Scripts, plug-ins, or control surfaces. Common no-go or not-yet areas in the current beta: - Real-time audio processing. - Real-time MIDI processing or monitoring while notes are played. - Synthesizers, samplers, audio effects, or devices inside Live's device chain. - Persistent background processes that observe changes indefinitely. - Programmatic triggering from Remote Scripts, OSC, keyboard shortcuts, or external controllers. - Rebuilding or rearranging Live's native UI. - Non-modal Extension windows. - Direct automation envelope editing; automation is not exposed in the current beta. - Full post-FX master export hooks; the SDK examples and API discussion emphasize specific render/resource workflows rather than replacing File -> Export. The SDK is beta. Treat API limits as moving targets. If a missing capability matters, file a beta feature request through Centercode or Ableton's official beta feedback channels. ## Requirements For users installing `.ablx` files: - Live 12 Suite Beta, version 12.4.5 or later. - A downloaded `.ablx` Extension file. - Live restarted after installation if the Extension does not appear. Extension packages are currently beta-only. Stable Live releases may not load these packages until Ableton ships Extension support broadly. Live Standard, Intro, and Lite are not supported for the current public beta Extension workflow. Versioned packages on extforlive.com are free to download for users who have access to the listed Extension. For developers: - Live 12 Suite Beta, version 12.4.5 or later. - Ableton Extensions SDK downloaded from Centercode. - Node.js v24.16.0 LTS. - A code editor such as VS Code, Cursor, or another editor. - Basic JavaScript/TypeScript familiarity, or an AI coding assistant with the SDK docs and this guide loaded. ## SDK Download Contents The SDK download is more than a single binary. Beginners should expect: - Bundled documentation in a `docs` folder. - Source-code examples. - An extension creation package such as `ableton-create-extension-1.0.0-beta.0.tgz`. - CLI tooling for building and packaging Extensions. Do not assume every SDK example is already a packaged `.ablx`. Some examples are source projects that you run or package yourself. ## Installing and Running an Extension 1. Download an `.ablx` Extension from Ableton's gallery, extforlive.com, or a trusted developer. 2. Open Live 12 Suite Beta 12.4.5 or later. 3. Install the Extension via Settings -> Extensions. 4. Restart Live if it does not appear. 5. Right-click the relevant object in your Set. 6. Open the Extensions submenu. 7. Choose the command. Important: Extensions do not appear in the Browser like Packs, devices, or samples. They appear in context menus only when the Extension supports the thing you clicked. Examples: - A MIDI helper may only appear when you right-click a MIDI clip or MIDI note context. - A track organization tool may appear on a track header. - A scene tool may appear on a scene. - A clip utility may not appear on an empty part of the Set. ## Developer Mode vs Installed Extensions - Developer Mode is for building and testing your own Extension. - Installed `.ablx` Extensions may not run while Developer Mode is enabled. - If installed Extensions show in Settings but do not appear in context menus, turn Developer Mode off, restart Live, and try right-clicking the correct object. ## Creating, Running, and Packaging From Source The exact commands can change during beta, so check the SDK's bundled docs first. These practical command patterns are common in early Extension projects: ```bash # Create an Extension project from the SDK tarball. npx 'file:/path/to/ableton-create-extension-1.0.0-beta.0.tgz' # Run a source Extension while developing. npm start # Some projects accept an explicit Live beta app path. npm start -- --live "/Applications/Ableton Live 12 Beta.app" # Package when the example includes a package script. npm run package # Fallback pattern discussed for examples without a package script. npm run build && extensions-cli package ``` Windows note: keep `file:` and the path together as one quoted argument when using `npx`, especially if the SDK path contains spaces. macOS note: avoid mixing shell escaping styles. Prefer quoting the app path as one string instead of escaping spaces inside quotes. ## SDK Concepts To Know These names and concepts are useful starting points when reading the official bundled docs. Treat this as a map of terms to look up, not as a replacement for the API reference. - `api.ui.registerContextMenuAction`: register actions for a Live context menu. - Context scopes: an Extension appears only where its registered context applies. - `context.application.song`: common entry point into the current Set. - `withinTransaction`: group Live mutations into a single undo step where supported. - `withinProgressDialog`: show progress for longer-running tasks. - `api.environment.storageDirectory`: persistent storage owned by the Extension. - `tempDirectory`: temporary working storage. - `importIntoProject`: copy/import files into the Live project before using them. - `createAudioTrack`, `createMidiClip`, `createAudioClip`: creation operations discussed in examples. - `clearClipsInRange`: useful for destructive clip-range operations; equal start/end values may be useful in split-like workflows where supported. - `deleteClip`: remove clips. - `renderPreFxAudio`: render pre-FX audio for supported workflows. Observed beta capability examples: - Read tracks, groups, and parent relationships. - Rename tracks. - Read/set volume. - Delete tracks. - Create audio and MIDI tracks. - Create audio clips from files. - Render or bulk-export pre-FX material in some workflows, usually into the project area. Observed missing or requested capabilities: - Reorder existing tracks. - Move existing tracks into groups. - Insert tracks at exact indices. - Set track colors. - Select tracks or the timeline. - Edit automation breakpoints/envelopes. - Write warp markers directly. - Trigger Extensions programmatically. ## Troubleshooting Checklist ### "I installed Extensions but nothing appears" Check these in order: 1. Are you on Live 12 Suite Beta 12.4.5 or later? 2. Are you using Suite, not Standard/Intro/Lite? 3. Is Developer Mode off? 4. Did you restart Live after installing? 5. Are you right-clicking the correct target: track header, clip, MIDI clip, scene, or another supported item? 6. Does the Extension Host show an error? 7. Did one Extension crash the host? Remove all Extensions, restart Live, then reinstall one by one. ### "I cannot find Settings -> Extensions" Most likely causes: - You are not using Live Suite. - You are not on Live 12.4.5 beta or later. - You opened a stable Live build instead of the beta build. - Your beta install is authorized against a non-Suite license. ### "The Extension Host stopped running" Likely causes: - One installed Extension crashed the host. - A known-bad or old Extension version is installed. - Node.js version mismatch. Practical recovery: 1. Remove recently installed Extensions. 2. Restart Live. 3. Reinstall Extensions one at a time. 4. Check ExtensionHost logs. 5. Confirm Node.js v24.16.0 LTS is the Node version Live is picking up. ### "I see an --allow-fs-write or Node-related error" Node version mismatches are a common cause. Install Node.js v24.16.0 LTS and make sure Live sees that version. Check `ExtensionHost.txt` logs if the UI only shows a generic host failure. ### "Where are the examples?" The SDK download includes source-code examples and a `docs` folder. Source examples are not necessarily packaged `.ablx` files. Downloadable `.ablx` examples are surfaced through the official Extensions page and extforlive.com. ### "Centercode never sent my verification email" Centercode verification emails can be delayed. Check spam, retry later, and try Google sign-in if email verification does not arrive. This is a beta-program access issue rather than an SDK issue. ## Security Model and Trust Extensions run in a separate Extension Host, so an Extension crash should not crash Live itself. This improves stability, but it does not make every third-party Extension safe. Practical installation guidance: - Only install Extensions from developers you trust. - Treat Extensions like plug-ins, scripts, or Max for Live devices: they are executable code. - Scan untrusted files with normal malware tools. - If something breaks, remove the newest Extension first and restart Live. - The host has sandboxing boundaries, but do not assume arbitrary downloaded code is harmless. Before installing a third-party Extension, look for: - Developer identity. - Source or repo link where possible. - Version. - Live beta compatibility. - Required permissions or filesystem behavior. - Whether the Extension reads or writes project files. - Whether network access is used. ## How to Think About the API The SDK is young, so build from supported contexts rather than assuming a complete replacement for Live's internal UI commands. A good Extension design starts with: 1. What did the user right-click? 2. What information can the Extension read from that context? 3. What discrete operation should happen? 4. What modal parameters does the user need before running it? 5. What should be created, modified, or returned? 6. What should happen if the selected object does not support the action? Avoid designs that need continuous listeners, real-time response, or permanent UI panels. ## Beginner Project Ideas Start with discrete, testable tasks: - Rename selected tracks from a convention. - Add suffixes or prefixes to stems. - Analyze a Set and report empty tracks, muted tracks, missing names, or arrangement length. - Create a MIDI variation from selected notes. - Detect a likely key from a MIDI clip. - Generate chord voicings into a selected MIDI clip. - Create empty tracks or placeholder scenes for a template. - Clear clips in a selected time range. - Import files into the project and create clips from them. - Export or render pre-FX audio from selected tracks when supported. - Build a Set preparation checklist modal. Avoid as first projects: - Real-time effects. - Anything that must run during playback. - Full UI replacement. - Audio plug-in behavior. - Non-modal editors that need live synchronization. - Deep operations not yet exposed by the SDK, such as direct automation envelope editing. ## Known Examples and Inspiration These early downloadable examples are listed on extforlive.com. Sign in to download packaged `.ablx` files; login protects the private package mirror from bot traffic. - [BBenCut](https://extforlive.com/extensions/bbencut): breakbeat and audio-slicing inspiration. - [Photo MIDI](https://extforlive.com/extensions/photo-midi): visual-to-MIDI sketching and generative composition. - [Notation](https://extforlive.com/extensions/notation): notation-oriented workflow support. - [Paulstretch for Live](https://extforlive.com/extensions/paulstretch-for-live): extreme time-stretching for ambient and sound-design workflows. - [Vivarium](https://extforlive.com/extensions/vivarium): playful generative ecosystem behavior. - [Beat Buddy](https://extforlive.com/extensions/beat-buddy): game-like companion behavior driven by Live material. - [Bird Game](https://extforlive.com/extensions/bird-game): interactive game actions that can become MIDI notes. - [RNMR](https://extforlive.com/extensions/rnmr): practical batch clip-renaming workflow. These are useful as inspiration, but beta Extensions can break as Live and the SDK change. If an Extension crashes the host, remove it and test installed packages one at a time. ## Common FAQ ### Do I need the SDK to use Extensions? No. You need the SDK to develop Extensions. To use a packaged `.ablx`, you need Live 12 Suite Beta 12.4.5 or later. ### Why are Extensions not in the Browser? They are context-menu commands. Right-click the relevant Live object. ### Can I trigger Extensions from shortcuts, OSC, Remote Scripts, or another program? Not in the current beta. They are triggered by user context-menu actions. ### Can Extensions run in the background? Not in the current beta. They are user-triggered and stop after their task. ### Can Extensions process audio in real time? No. Use Max for Live, plug-ins, or Live devices for real-time audio and MIDI behavior. ### Can Extensions edit automation envelopes? Automation envelope editing is not exposed in the current beta. ### Can Extensions create their own UI? They can show modal UI for parameters. They cannot currently create persistent non-modal panels or rearrange Live's native UI. ### Can Extensions interact with Max for Live? They run in their own process and should not be treated as an M4L bridge. ### Are Extensions safe? Only install code from sources you trust. Extensions are executable code. The host is separate from Live for stability, but third-party code still carries risk. ## Glossary - `.ablx`: Packaged Ableton Extension file. - Extension Host: Separate process that runs Extensions. - Developer Mode: Live setting for developing Extensions; turn it off when testing installed `.ablx` files. - Context menu: The right-click menu where Extension commands appear. - Target context: The kind of Live object an Extension action applies to. - SDK example: Source code included with the SDK; not always a packaged `.ablx`. - Live 12 Suite Beta 12.4.5: First public beta target for Extensions. ## Source Notes This resource summarizes: - Ableton's official Extensions SDK public beta page. - Ableton's official Extensions page and FAQ. - Ableton's Extensions SDK announcement/blog. - Practical beta usage notes and early Extension behavior. Because the SDK is in public beta, re-check the official SDK docs and bundled SDK documentation before relying on any API limit in production.