Chromebook audio editing: the three routes and their trade-offs

A Chromebook is mostly a browser, so browser-based audio tools are not a compromise here. They are the native option, and they run at full speed with nothing installed.

They handle the common jobs well: trimming, splitting, converting formats, boosting volume, removing background noise, and for spoken audio, editing through a transcript.

Two things to check. Whether the tool works offline, since some do everything locally in the browser and others need a connection. And what happens to your file, because uploading someone else's recording to an unknown service is worth thinking about first.

Hilite records and edits in the browser and works on ChromeOS, and we make it, so weigh that as you like.

Most Chromebooks run Android apps from the Play Store, which opens up mobile audio editors. They work, and they are designed for a touchscreen and a phone-shaped display.

On a Chromebook with a trackpad and a wide screen, that often means a cramped interface in a window that does not resize sensibly. Some apps handle it well; many do not.

File access is the other friction. Android apps see a separate storage area from ChromeOS, so moving files between the two takes an extra step through the Files app.

Worth trying if you already know a particular Android editor. Not worth learning one specially.

ChromeOS can run a Linux container, and inside it you can install Audacity and get a complete desktop audio editor: multitrack, noise reduction, compression, EQ, batch export.

Turn it on in Settings under Developers, then Linux development environment. Once it is running, install Audacity from the terminal or through a package manager.

Two real caveats. Audio device access from inside the container has historically been awkward, so recording directly may not work even when editing does. And the container needs disk space, which entry-level Chromebooks do not have much of.

On a managed school or work device, the Linux option is very often disabled by policy, and that is not something you can turn on yourself.

Recent ChromeOS versions include a Recorder app, which is enough for a single voice with no editing and is already installed.

Browser recorders work too, using the same microphone permission any site asks for. That is usually the better route because the recording lands somewhere you can immediately edit it.

The built-in microphone on most Chromebooks is poor, sitting far from your mouth and pointing away from you. Even cheap wired earbuds with an inline microphone are a real improvement, because closer beats better almost every time.

USB microphones generally work on ChromeOS without drivers. Plug it in and select it in the site's microphone permission dialogue.

School and work Chromebooks are managed by an administrator, and the Linux container and Play Store are commonly switched off. That removes two of the three routes above.

Browser tools are usually still available, since they are just websites, though some networks block categories of site and you may need a specific one allowed.

If you are a student with a podcast assignment, ask the IT department to allow the tool you want rather than trying to work around the restriction. It is a reasonable request and usually granted.

If nothing is available, record on a phone and edit there, then submit the file from the Chromebook. Not elegant, and it works.