Native vs converted NAM: what's the difference?
“NAM compatible” can mean very different things. Here is how we classify each device.
Native
The device runs the NAM model itself. Nothing is re-encoded — you hear the same model the desktop plugin runs. NUX describes it as: “The device runs the NAM model itself. Nothing is re-encoded.”
Converted
The device (or its editor app) reads the .nam file and re-encodes it into the maker's own format — e.g. Valeton's SnapTone or Hotone's format. What you hear is an approximation whose quality depends on the converter.
A2-Full vs A2-Lite
Since 2026-06-02, A2 is NAM's standard architecture. One A2 file contains both sizes. A2-Full is the maximum-accuracy version for DAWs and powerful hardware; TONE3000 says it uses 30–40% less CPU than A1. A2-Lite targets embedded hardware; TONE3000 says it runs at 50% CPU on a 600 MHz ARM Cortex-M7. A2 is not backward compatible: older plugins/firmware can't load A2, but A1 files still work in A2-capable hosts.
Sources: TONE3000 A2 launch · NUX: what native means · Gearnews guide · neuralampmodeler.com: A2 is released
How we label status
- A2-Full native Runs NAM A2-Full natively (no conversion)
- A2-Lite native Runs NAM A2-Lite natively
- A2 native (variant n/s) Runs NAM A2 natively; source does not say Full vs Lite
- Converts files Imports NAM files but converts them to a proprietary format
- NAM v1 only Runs NAM A1 only
- Announced A2 support announced, not shipped
- None No on-device NAM
- A2 unverified Loads NAM; A2 status not confirmed by a primary source
When sources disagree, we prefer the manufacturer's own release notes, then official partner posts (e.g. TONE3000), then retailers and press — and we show the disagreement on the device page.