what is the Ableton Extensions SDK?
on June 2, 2026, Ableton shipped the Extensions SDK. it’s a free, open toolkit that lets you write code that reads and rewrites a Live Set from the inside.
if you’ve wanted Live to do something it doesn’t do, you can now build it.
what it is
the Ableton Extensions SDK is an open JavaScript toolkit for building custom tools that run inside Live 12 Suite. it shipped as a free public beta. you write extensions in JavaScript or TypeScript — the languages the web already runs on.
it’s built on Node.js (the SDK targets v24.16.0 LTS). no new language to learn, no patching environment to master. the editor and tools you already use carry over.
what an extension can do
an extension reads and edits the structure of a Set: tracks, clips, parameters, automation. it doesn’t just read. it rewrites.
if you know Max for Live, this is familiar: typed access to the Live Object Model, the same model Max for Live works against. the exposed scopes include AudioClip and MidiClip, AudioTrack and MidiTrack, ClipSlot and Scene, plus devices like Simpler, Sample, and DrumRack. you walk the tree, read what’s there, change it.
how you actually use one
extensions live in the right-click menu. select something in your Set: a clip, a track, a range. right-click, and the extensions that apply show up as actions. pick one. if it takes options, a small dialog opens first.
no device to drag in. no instance to load. an extension is available everywhere, all the time. it behaves less like a plug-in and more like a command you added to Live.
the interfaces you can build
you’re not stuck with a menu item. the SDK gives you a few surfaces:
- right-click actions — items in the contextual menu.
- modal dialogs — for input and confirmation.
- webviews — full custom interfaces in HTML, CSS, and JavaScript.
the dev loop is fast. a dev host applies your changes live, so you don’t restart Live to test. an npm-based wizard scaffolds a new project from the terminal.
what people are building
“read and rewrite the Set” covers a lot. early extensions:
- transform and generate MIDI
- analyze song and track structure
- automate repetitive, click-heavy work
- make generative patterns
- connect Live to outside services
- render audio from the Arrangement
- strip silence
- swap warp modes from the right-click menu
- import files into a project
Ableton’s Explore gallery collects examples — things like Paulstretch for Live and Notation — if you want to see the range.
what you need to try it
three things:
- Ableton Live 12 Suite Beta,
12.4.5or later. Suite only — not Standard, Intro, or Lite. - Node.js.
- a code editor. VS Code works.
the SDK and its docs are free.
what it can’t do yet
it’s a public beta. the edges are real. right now an extension can’t:
- talk to Max for Live directly
- reach Tuning Systems
- run on its own — no startup or on-completion triggers; you invoke it
- drive hardware or control surfaces
expect some of this to move as the platform and the community push on it.
extensions vs Max for Live
they don’t compete. Max for Live builds devices — instruments, audio and MIDI effects — by patching, and it sits in the signal path while you play. extensions act on the structure of a Set: code that walks your tracks and clips, changes them, then gets out of the way.
coming from another DAW, the closer match is scripting: ReaScript in Reaper, the scripting in Renoise, Ardour’s Lua API. same idea, in JavaScript, for Live.
licensing and community
anyone can build and share extensions under the Ableton SDK license. one caveat: Ableton takes no responsibility for unofficial extensions, so treat code from strangers like code from strangers.
there’s a Discord where people share and test builds. docs and example projects are at ableton.github.io/extensions-sdk.
where this goes
the ecosystem is days old. a whole class of “things Live couldn’t do” is now buildable, and the people building it are deciding what it’s for.
we’re building one. flow as is — an Ableton Extensions SDK plugin, in development.