1. .dw represents the project, not an audio render
A .dw file keeps the editable project state: structure, notes, settings, automation, and data required to return to the studio. It does not replace a final WAV, and a WAV cannot restore editable project state like a .dw can.
2. Cross-device without project conversion
The principle is one project contract. The same .dw is intended to open on Desktop and Android; there is no reduced mobile project that must be generated between them.
3. Verify after transfer
After moving a file between devices, open it and quickly check important tracks, instruments, samples, and the start of the arrangement. A thirty-second verification is better than discovering an issue later.
TIPS
Keep these in mind
- Keep dated versions.
- Do not overwrite your only working copy during a transfer.
- For listening, export audio too; for continued editing, keep the .dw.
AVOID
- Assuming an audio file replaces the project.
- Deleting the source before verifying the copy.
- Clearing browser data before exporting important projects.