Do you need a DAW to prepare audio files?

If you receive production sound and only need to turn it into files your editor can use, you may be opening a digital audio workstation for jobs that never required one. That does not mean DAWs are overpriced or replaceable. It means two different kinds of work are being done with the same tool, and only one of them needs it.

This article separates the two honestly: what a DAW is for, what file preparation is, and where a browser-based toolkit like this one is enough — including the cases where it is not.

What a DAW is genuinely for

A workstation exists to make decisions about sound. Pro Tools, Nuendo, Reaper, Audition and Resolve Fairlight all share the same core purpose: a timeline, a mixer, plugins, automation and sync to picture. Everything in that list is about judgement, not mechanics.

• Dialogue editing, alternate takes, fades and edits against picture.
• Mixing: levels, panning, EQ, compression, reverb and automation.
• Restoration: noise reduction, de-clicking, spectral repair.
• Loudness compliance and broadcast deliverables that must be measured and signed off.
• Sound design, layering, pitch and time manipulation.
• Anything where you need to listen, decide and revise.

If your task appears above, use a DAW. No browser tool substitutes for a mixer, a plugin chain, a loudness meter or a timeline synced to picture.

What file preparation actually is

File preparation is the mechanical layer underneath the creative work. It is rules-based: the correct result is defined before you start, and there is nothing to judge by ear.

• Splitting a polyphonic WAV from a field recorder into named mono tracks.
• Merging separate mono recordings back into one multichannel file.
• Reordering or renaming channels so they match a delivery spec.
• Converting sample rate or bit depth for a specific deliverable.
• Extracting the audio track from a camera or screen-recording file.
• Inspecting a file to confirm sample rate, bit depth, channel count and duration before sending it on.

These are the tasks most independent filmmakers, video editors and assistant editors actually perform when they open a workstation. Import, split, export, close. The mixer is never touched.

Why people use a DAW for prep anyway

Usually because it is already installed and it works. That is a legitimate reason. The costs are not in the licence, they are in the overhead around each small job:

• Launching the application and waiting for a plugin scan.
• Creating a session and choosing a sample rate before you have seen the file.
• Importing, routing and configuring a bounce for a mechanical export.
• Needing the application present on whichever machine you are sitting at — a rented workstation, a client's edit suite, a locked-down laptop without admin rights.

None of this is difficult. It is simply disproportionate to the job when the job is copying samples from one container into another.

The configuration mistakes that cost the most

Free workstations such as Resolve Fairlight or Reaper's evaluation mode will happily convert anything, so cost is rarely the deciding factor. The real bill from using a session-based tool for prep is rework, and it comes from configuration rather than skill:

• A session created at 44.1 kHz silently resampling 48 kHz rushes.
• A poly file summed to stereo on import, losing tracks that cannot be recovered from the bounce.
• A bounce at 16 bit when the deliverable asked for 24 bit.
• Channels exported in the wrong order, which the editor discovers days later.

Every one of those is found downstream, by someone else, and costs a re-export plus a conversation. A tool that shows the source sample rate, bit depth and channel layout before you export removes most of that category, whatever tool you choose.

What a browser toolkit can and cannot do

Audio Tool Kit runs entirely in the page using the Web Audio API and JavaScript encoders. Your files are read and rewritten on your own machine; audio is not uploaded to a server. That matters on NDA projects, where many online converters are a legal problem before they are a technical one.

It is narrower than a DAW on purpose. Honest limits:

• No mixing, plugins, automation, timeline editing or loudness metering.
• Non-WAV sources are decoded by your browser's own codecs, so the decoded sample rate can differ from the file's nominal rate.
• Sample rate conversion uses linear interpolation without dithering, which is fine for delivery prep but is not a mastering-grade resampler.
• MP3 export is fixed at 320 kbps and a maximum of two channels.
• Large files are limited by your browser's available memory, not by a server queue.

Within those limits the work is deterministic. Splitting and merging WAV at the source sample rate and bit depth is a sample copy, so the audio data in equals the audio data out.

Cost, without invented numbers

DAW pricing changes, varies by region and by plan, so treat any figure you read online as something to verify with the vendor. The structural difference is what matters: most professional workstations are sold as subscriptions or as licences with paid upgrade cycles, plus optional plugin bundles. That model is sound when the software is open every day.

Audio Tool Kit is priced for occasional, mechanical work: the first conversion is free, additional conversions are €0.90 each, and Pro is a single €19.90 payment with no subscription. If you split rushes twice a year, pay-per-use fits that reality better than a permanent licence. If you mix five days a week, your workstation is already paying for itself and nothing here changes that.

A practical rule

Creative audio work belongs in a DAW. Technical file preparation does not need one. Most working setups use both: prepare and inspect files in the browser, then open the workstation when there is a decision to make.

• Use a DAW when: mixing, editing dialogue to picture, restoration, plugin processing, loudness-compliant delivery.
• Use a browser toolkit when: splitting or merging, mapping channels, converting rate or depth, extracting audio from video, checking what a file actually contains.
• Use both when: you prep on a machine that does not have your DAW installed, or you want the mechanical step done before the session is even created.

Where to start

Pick the task rather than the software. If you have a poly WAV and an editor asking for mono files, start with the PolyWAV splitter. If you are unsure what you have been sent, inspect it first and decide afterwards.