Frequently Asked Questions

This is almost always one of four things:

• Wrong format — Make sure you selected the correct console model in the export dropdown. An X32 .scn file will not load on a Yamaha, and vice versa.
• USB format — Most consoles require FAT32 formatted USB drives. If your drive is formatted as NTFS or exFAT, the console may not recognize it. Reformat the drive to FAT32 (you can usually do this from the console itself).
• File location — Some consoles expect files in a specific folder on the USB drive. Check your console's manual for the correct path.
• Firmware version — Older firmware may not support newer file formats. Check if a firmware update is available for your console.

Every console has a maximum number of characters it can display on its scribble strips. load·in auto-abbreviates long names to fit, but you may want to customize them.

If names are getting cut off, shorten them in the Inputs tab before exporting. Common abbreviations: "Kick Drum" becomes "Kick", "Acoustic Guitar" becomes "Ac Gtr", "Lead Vocal" becomes "Ld Vox".

First: If you have a Pro license with cloud sync enabled, your plots may be recoverable from the cloud. Open load·in and check if they appear after syncing.

Free users: load·in stores plots in your browser's local storage. Clearing your browser data (history, cookies, cached files) will delete them. This is why we recommend exporting important plots as GFS files (load·in's native format) to your file system.

Prevention: Get in the habit of exporting a GFS backup of important plots. Files tab → Export As → GFS. Pro users get automatic cloud backup, so this is less of a concern.

Each console has its own color palette, and they are not identical across brands:

• X32/M32: 16 colors (Red, Green, Yellow, Blue, Magenta, Cyan, White + light variants)
• Yamaha CL/QL: Different palette — "Red" on X32 may appear slightly different on a Yamaha

load·in picks the closest available color for each console. The mapping prioritizes readability: drums get warm colors, vocals get cool colors, DI inputs are neutral.

Yes. load·in currently imports these supported file types:

• .scn files from Behringer X32/Midas M32 and Behringer WING
• .snap files from Behringer WING
• .clf files from Yamaha CL/QL
• .ses files from DiGiCo SD series
• .txt files for generic input lists

The format is auto-detected. Just select your file and load·in figures out the rest. See the Console Import guide for full details.

Yes, completely. load·in is a Progressive Web App (PWA) that works offline after your first visit. All data is stored locally on your device. You can build, edit, and export stage plots with zero internet connection.

No cloud dependency, no login required. On mobile, you can tap "Add to Home Screen" for a native app-like experience that works offline.

load·in currently supports these console families and export targets:

• Behringer X32 / Midas M32, X-Air, and WING
• Yamaha CL / QL, DM3, and RIVAGE PM
• DiGiCo SD series
• Avid VENUE S6L
• Allen & Heath SQ and dLive
• DAW template export for labeled recording-session setup

New files made in load·in should preserve the fixtures and channel work you create in the app. Imported console files are handled conservatively, but exact carry-through can vary by desk model, firmware, and fields the manufacturer does not document. Keep backups of production files and test the exported file on the intended desk or editor before show time. See the Console Export guide for per-console instructions.

Free tier: Fully functional with up to 3 saved plots, watermarked PDF/PNG exports, and free X32-family (X32/M32/X-Air) native scene export. No credit card required.

Pro: $99 one-time purchase, yours forever. Unlimited plots, clean exports, cloud sync, shareable links, native console exports for every other desk, DAW template export, and supported format updates. No per-seat charges.

See the load·in pricing for current details.

In load·in, tap the upgrade prompt or go to the Files tab. On iPhone and iPad, subscribe or restore through the App Store purchase controls. On the web app, use the web checkout and license recovery flow. See the Pro Features guide for full details.

Yes. load·in works on any device with a modern browser — phone, tablet, laptop, or desktop. It is mobile-first, meaning the interface was designed for touch screens first and then scaled up for larger displays. Many operators use it on a tablet at front of house or on their phone during load-in.