Cover image for The file conversion tools I actually reach for (instead of installing FFmpeg again)

AhaConvert

Every few months I hit the same wall. A client sends over a .mov file that needs to end up as an .mp4 for a web page, or someone drops a .heic photo in Slack and asks why it "won't open" on their Windows machine. My first instinct used to be brew install ffmpeg and then spend twenty minutes remembering the flags. These days I don't bother unless the job actually needs scripting or batch automation.

Here's what's actually in my rotation, and when I reach for each one.

When it's a one-off file and I just need it done

If I'm not going to touch this format again for another six months, I'm not installing anything. Browser-based converters have gotten good enough that for a single file, they're just faster.

CloudConvert is usually my first stop for anything document or spreadsheet related — it handles a wide range of formats and the interface doesn't get in the way. AhaConvert is what I use when it's image or audio work specifically; it's fully browser-based, no account needed, and it deletes uploaded files automatically after 24 hours, which matters if the file has anything client-confidential in it. Neither one requires me to think about dependencies or version conflicts, which honestly is 90% of why I use them.

For quick audio grabs — pulling an MP3 out of a video file someone sent, or converting an old .wma voice memo — I've had good results with Online-Convert too. It's not pretty, but it's reliable and doesn't nag you to create an account.

When I need to batch-process a folder

This is where the browser tools stop being useful and FFmpeg earns its keep. If I'm converting 200 images or normalizing audio levels across a podcast archive, nothing beats a script I can rerun.

for f in *.wav; do
  ffmpeg -i "$f" -acodec libmp3lame "${f%.wav}.mp3"
done

Enter fullscreen mode Exit fullscreen mode

I know this loop by heart at this point. If you're doing this regularly, it's worth the setup pain once and never thinking about it again.

When it's part of a pipeline

If file conversion is happening inside an app — say, a user uploads a file and your backend needs to normalize it before storage — that's a different problem entirely. You want a library, not a tool. sharp for image processing in Node, Pillow in Python, or FFmpeg wrapped in a queue worker if you're dealing with video or audio at scale. Don't reach for a web tool here; you need something your code can call directly and that fails predictably.

The actual decision tree

Honestly it comes down to three questions:

  1. Is this a one-off? Use a browser tool. Don't install anything.
  2. Am I doing this more than twice a month? Script it with FFmpeg or a CLI tool once, save yourself the repeated manual work.
  3. Is this inside an application? Use a library, not a tool — you need error handling and control that a web UI can't give you.

Most format headaches devs run into are actually category 1 and people treat them like category 2 out of habit — installing something "just in case" for a file they'll never touch again. I used to do the same thing until I noticed how much disk space and mental overhead I was carrying around for tools I opened twice a year.

Curious what's in other people's rotation — anyone still swear by a desktop app for this, or has everyone moved to browser tools for the occasional one-off?