Importing from TONE3000

TONE3000 (formerly ToneHunt) is the largest community library of Neural Amp Modeler captures — thousands of amps, pedals, and full rigs, captured by artists and shared under a range of licenses. Axion connects to it directly: link your TONE3000 account once and import any capture you have access to with a couple of clicks, instead of downloading a .nam, unzipping it, and dragging it in.

TONE3000 import is free on every tier — it's part of NAM loading, which is free for everyone. It's available on the web app and Axion Desktop; the plugin doesn't do in-DAW sign-in, so import there from the web or Desktop and the capture is in your library everywhere.

Connecting your account

Open the amp's source toggle → Manage NAM library, then click Import from TONE3000…. The first time, Axion opens a TONE3000 sign-in window. Approve access and the window closes itself — you're connected. Axion stores only the session token needed to fetch captures on your behalf; your TONE3000 password never touches Axion.

The connection persists, so subsequent imports skip straight to the picker. If your session expires you'll be asked to reconnect — same one-click flow.

Importing a capture

1. Click Import from TONE3000…. A TONE3000 window opens for you to pick a tone (use its search and filters).
2. Pick a tone. Axion shows that tone's available models. Many tones publish several — different architectures (A2 / A1) and sizes (Standard, Lite, Feather, Nano). Axion pre-selects the recommended one (newest architecture, full size) and marks it.
3. Choose what to bring in:
   • Add to library — imports the checked model(s) into your NAM library without changing your current sound. Tick several to grab a whole set at once.
   • Add & load — available when exactly one model is selected; imports it and switches the amp to it immediately so you land back on the rig hearing it.

Imported captures live in your browser's IndexedDB exactly like a hand-added .nam — they persist across reloads and work offline once imported. Re-importing the same capture is a no-op (Axion content-addresses by hash, so there are no duplicates).

TIP Not sure which size to pick? Start with the recommended A2 model. If you hear crackle on a lower-powered machine or the mobile baseline, re-import the Lite or Feather variant — it's roughly half the CPU for a small fidelity trade.

License and attribution

Every TONE3000 capture carries its license and the artist who made it. Axion shows both on the model's library row, along with a view on TONE3000 link back to the source tone and a "Powered by TONE3000" credit. The same license and attribution travel with the capture if you reference it in a shared preset — so credit is never lost.

Respect each capture's license. Some are permissive (CC-BY family); others are marked TONE3000-only or are commercial packs with their own terms. Axion surfaces the license so you can.

How TONE3000 captures travel

Axion never re-hosts TONE3000 weights — every capture is fetched from TONE3000 under your own account. That has two consequences worth knowing:

• Shared presets. When you share a preset that uses a TONE3000 capture, the .nam itself isn't sent — only a reference (the tone, the model, and its hash). A recipient who opens it re-fetches the capture from their own TONE3000 account. If they're not connected, or no longer have access, the preset falls back to the analytical-clean amp with a prompt to import it. See Sharing a preset.
• Cloud NAM storage. TONE3000 captures follow you across devices as references, not stored files — each device re-downloads them from your TONE3000 account. Only your own captures are stored as files. This keeps Axion out of redistributing third-party weights entirely.

When an import won't complete

• Not connected / session expired — reconnect via the Import from TONE3000… button; it re-runs the sign-in.
• The tone has no NAM models — Axion only imports NAM captures. Tones for other platforms (or with no published model files) can't be imported; pick a NAM capture.
• The capture won't play after importing — that's a NAM-side issue, not a TONE3000 one; see Loading a NAM model for the CPU and format notes.