Built for the rig you already own
Every recipe is translated into the exact block names and parameter values your modeler expects. Pick your unit and start playing.
Helix
The amp-modeler that rewrote the rulebook on live guitar tone.
Open the manualQuad Cortex
Neural captures meet powerful modeling in a pedalboard-sized powerhouse.
Open the manualTONEX
AI-powered Tone Models that capture the soul of real amps and pedals.
Open the manualFractal
Studio-grade amp modeling with surgical precision and endless routing.
Open the manualKemper
The original profiling amp. One box, every amp you have ever played.
Open the manualBoss Katana
Affordable, gig-ready modeling with a hidden depth that rewards digging in.
Open the manualWhat gets translated
A tone recipe starts as the physical rig: the guitar and pickup position, the pedals in front, the amp and its knob positions, the cabinet and where the mic sat. That chain is the source of truth. Every platform page below is that same chain re-expressed in the block names and parameter ranges your unit actually uses — a Tube Screamer becomes a Screamer on Helix and a TS808 on Fractal, and the drive knob is converted into whatever scale that block reports, not copied across as a number that happens to look right.
Where you get a file, and where you get settings
Helix, Quad Cortex, and Boss Katana recipes build a preset file you can import — a .hlx, a bundle, or a .tsl— because those formats are documented well enough to write correctly. TONEX, Fractal, and Kemper recipes give you the full block list and every value to dial in by hand. That split is a limitation of the file formats, not of the research behind the recipe, and it's marked on each recipe before you click anything.
What survives the port, and what doesn't
Gain structure, block order, and the relationships between settings port cleanly: if the amp is on the edge of breakup with a boost slamming the front, that survives on every platform. Exact captures don't. A Kemper profile of a specific 1959 Bassman and a Helix model of the same amp are different pieces of software, so the recipe gives you the closest model plus the settings that get its behaviour into the same place, not a claim that they are identical. Where a platform has no equivalent block at all, the chain says so rather than substituting something quietly.
Don't own a modeler?
The pedalboard view drops the translation layer and shows the original hardware chain — real pedals, real amp, real settings. It's the same recipe, which is the point: the modeler versions are derived from it, not the other way round. You can also put two chains next to each other on the compare page to see how a rig changes from one player to another, or start from the full archive.