An open-source editor for the Axe-Fx II, rebuilt from scratch in pure Rust.
The routing grid, every block's pages and knobs, scenes, X/Y, tuner, tempo and looper,
in a small native app for Windows, macOS and Linux. Free, offline, and yours.
A preset on the routing grid, with the amp block's Basic page open. Captured from the real app, connected to an Axe-Fx II XL.
Install · Features · Everything in the box · Agents · Under the hood · Build from source · Roadmap · Contributing
Important
Status: early alpha. Axe-Grid edits presets on real hardware today, but it is not yet a replacement for the original editor: modifiers are new, and there are no global settings and no meters. It has been tested on one Axe-Fx II XL (firmware 32.00) on Windows; the macOS and Linux builds compile from the same code but nobody has run them against a unit yet. ROADMAP.md says exactly where things stand. Back up your presets before pointing any new editor at an instrument you depend on.
| Preset and scenes across the top, the 12×4 grid in the middle, the selected block's pages underneath. Every control is on the page and row where your hands expect it. | One executable of a few megabytes. No runtime, no web view, no drivers or services. Starts in a moment and stays out of the way. | Talks to the unit over whatever MIDI port your computer offers: USB where the system provides one, or a plain 5-pin MIDI interface. | Every action is a command, so the same engine can be driven from the window, the command line, a JSON control channel or an MCP server. |
No programming tools are needed. Pick your system, download one file, and run it.
-
Open the latest release.
-
Download the file for your computer:
Your computer Download Then Windows 10 or 11 axe-grid-<version>-windows-x64.zipUnzip it, open the folder, double-click axegrid-setup.exe: it puts Axe-Grid on your desktop and in the Start menu. (Or just runaxegrid.exefrom the folder.)Mac (Apple silicon or Intel) axe-grid-<version>-macos-universal.zipUnzip it, drag Axe-Grid to Applications, then right-click it and choose Open the first time Linux (64-bit Intel/AMD) axe-grid-<version>-linux-x86_64.tar.gzUnpack it and run ./axegridLinux (64-bit ARM) axe-grid-<version>-linux-aarch64.tar.gzUnpack it and run ./axegrid -
Connect your Axe-Fx II and switch it on, then start Axe-Grid. It looks for the unit by itself, on USB first and then on your MIDI interfaces. If it does not find it, press Find my Axe-Fx, or choose the MIDI ports at the top of the window and press Connect. No unit at hand? Press Simulator to look around.
Windows and macOS will warn you the first time, because the builds are not yet signed with a paid certificate. The step-by-step guide shows what to click, how to connect the unit, and what to do when it is not found: docs/install.md.
Every screenshot here is the real app, connected to an Axe-Fx II XL.
| Step through presets or jump to a number · rename · save, with a confirmation that names the slot being overwritten · a browser of every slot with search, copy, export, import and backup · eight scenes · tempo, tap and CPU load. | Place, move and remove blocks and shunts · cable and uncable cells · one-click runs to the input and the output · cables follow a block moved within its column. | Pages for 38 block types · bypass and X/Y · knobs, faders, switches and lists with the unit's display text · amp, cab and effect type lists read from your unit · undo and redo · curves for the EQs, filter, compressor, gates and more · looper and Tone Match buttons. | ||
| On an XL or XL+: the names of all 1024 user cabs · export to a file · import a file into a slot · try a cab in the preset's cab block. Import is new and not yet confirmed on a unit. | ||||
| A built-in stand-in device with three presets. Try the whole editor, write scripts and run the test suite with nothing plugged in. | Edits go to the unit's edit buffer, exactly like turning its front-panel knobs. Nothing is written to a preset slot until you press Save and confirm. |
spec/SPEC.md documents the Axe-Fx II SysEx messages Axe-Grid uses, each fact tagged with how it was verified, for anyone building their own tools.
|
New and still to be confirmed on a unit: scene and block copy and paste, the looper's position bar and the Tone Match steps. Not there yet: resetting a block, bank files, meters and global settings. The full list, ranked, is in ROADMAP.md.
Every menu item, button, knob and shortcut runs a command from one registry of 83 commands
(docs/commands.md). The window, the CLI, the JSON control channel and the MCP
server all call the same commands, so anything you can click, a script or an AI agent can do too.
# List every command with its parameters, as JSON
axegrid-cli commands
# Try a command against the built-in simulator
axegrid-cli --simulator run block.select '{"block":"Amp 1"}'
# Run a list of steps from a file
axegrid-cli batch steps.json
# Let an agent drive it over MCP (headless, or bridged to the running window)
axegrid-cli --simulator mcpThe desktop app also offers an authenticated, loopback-only control channel
(axegrid --control <port> --control-token-file <path>), so a script or agent can drive the window
you are looking at. See docs/control-protocol.md and
docs/mcp.md.
- Engine first: editor state and a command registry, with a thin egui window on top. Six crates
in strict layers, from SysEx framing up to the UI (
docs/architecture.md). The engine talks to the unit on a thread of its own, so a slow or silent unit never freezes the window. - Never crash: no
unsafe, and nounwrap,expectorpanic!outside tests. A device that answers garbage, or not at all, produces an error message, not a crash. - Tested without hardware: 187 tests run against the simulated device, including hostile command parameters and literal bytes captured from a real unit.
- Clean-room: written from a functional specification and observed behaviour. No code, artwork,
fonts or skins from the original editor (
docs/clean-room.mdlists the two data files that originate in the original). - Evidence over guesses: every wire-format fact in the spec carries a confidence tag, and what
has and has not been checked on hardware is listed in
docs/gaps.md.
You need Rust 1.95 or newer. On Linux, also install the ALSA headers
(sudo apt install libasound2-dev pkg-config on Debian and Ubuntu; other distributions are in
CONTRIBUTING.md).
git clone https://github.com/RamonWide/axe-grid
cd axe-grid
cargo run --release -p axegrid # the desktop app; press "Simulator" to try it
cargo test --workspace # the test suite; no hardware neededNew contributors and AI agents: start with AGENTS.md, then
CONTRIBUTING.md.
| For | Read |
|---|---|
| Installing and first steps | docs/install.md |
| Where the project stands | ROADMAP.md, docs/gaps.md, CHANGELOG.md |
| Contributing | CONTRIBUTING.md, AGENTS.md, CODE_OF_CONDUCT.md |
| How it is built | docs/architecture.md, spec/SPEC.md, docs/clean-room.md |
| Scripting and agents | docs/commands.md, docs/control-protocol.md, docs/mcp.md |
| Security | SECURITY.md |
| Making a release | docs/releasing.md |
- Something does not work: open a bug report. Say which Axe-Fx II model and firmware you have, and which operating system.
- You own a unit and want to help: the most useful thing is to confirm how your model behaves. See Hardware reports.
- Questions and ideas: Discussions.
Axe-Grid is released under the MIT License. Copyright (c) 2026 The Axe-Grid contributors.
Every file not written for this project is listed with its origin in ATTRIBUTION.md. The app icon and all interface artwork are original to this project.
Axe-Fx, Axe-Edit and Fractal Audio are trademarks of Fractal Audio Systems, LLC. Axe-Grid is an independent, open-source project and is not affiliated with, sponsored by or endorsed by Fractal Audio Systems; these names are used only to describe the hardware it works with. Axe-Grid comes with no warranty: you use it with your own equipment at your own risk.





