DAWWW-CORE / BROWSER DAW FAQ

Questions about the DAW, not the cloud.

DAWWW-CORE is a local-first browser music-production workstation. Desktop is available now without a payment flow; Android is the upcoming subscription surface for the same portable .dw project model.

Is DAWWW-CORE free on Desktop?

Yes. Desktop is currently available directly in the browser with no payment flow.

Is it a full browser DAW?

It combines sequencing, detailed step editing, piano roll, arrangement, mixing, routing, automation, built-in instruments/effects, portable project I/O and audio export.

Where are projects stored?

Working projects are local-first and primarily stay on the device. Exported .dw files provide the portable project copy for transfer, archive and recovery.

Does it need cloud project storage?

No. Cloud project storage is not required for a DAWWW-CORE project to exist or for project portability.

Can the same project move between Desktop and Android?

Yes. Desktop and Android use the same complete .dw project model: no reduced mobile format and no conversion step.

How many instruments are built in?

51: 50 dedicated sound engines plus a sampler, spanning drums, basses, electronic synths, pads, keys/bells, guitars and orchestral instruments.

How many effects are built in?

16, including parametric EQ, compressor, convolution reverb, tempo-synced delay, modulation, distortion, filtering, dynamics, saturation, bitcrushing and utility processing.

Is DAWWW-CORE open source?

The production source remains private. The public GitHub repository is a product showcase with screenshots, releases, specialized pages and feedback.

Does it work offline?

The workstation is local-first and PWA-oriented. Normal audio runs on the device; offline availability depends on cached app assets, browser support and local storage.

How large can a session be?

There is no artificial universal track-count cap. Practical capacity depends on CPU, memory, browser storage, polyphony, samples, effects, routing and export workload.