The browser-based tools I reach for when I need to compress a video, convert a file, trim audio, or shrink an image or PDF without installing anything.
My laptop is full of tools I used once. A video converter for a single project. A PDF utility I needed for one contract. An audio editor I opened twice.
These days, for one-off media tasks, I try a browser tool first. It's faster than installing something, and nothing is left behind to update or uninstall.
Here's how I decide when to use a web tool, when to write a script, and which tools I use by category.
Disclosure: I work on VideoBee, which appears in the video section. I've tried to be fair about where it fits and where other tools are better.
How I choose a tool
Before I use any online tool, I check:
- Does it handle my file size? Many tools silently cap uploads. This matters most for video.
- What happens to my file? For anything sensitive (client work, private recordings), I prefer local tools.
- How many steps? If it takes more than a few clicks, a script is probably better.
- Does it need an account? For a one-off task, I'd rather not.
- Is the output predictable? Re-encoding, metadata changes, and quality loss should be controllable.
When to use a web tool vs. a script
| Situation | My choice |
|---|---|
| One-off task, one or two files | Web tool |
| Same task every week | Script (FFmpeg, ImageMagick, etc.) |
| Batch of dozens or hundreds of files | Script |
| Sensitive or confidential files | Local tool or script |
| Quick check on a machine that isn't mine | Web tool |
| Needs to run in CI or a pipeline | Script |
Video
Video is where installing software feels the most disproportionate. Full desktop editors are huge, and FFmpeg's flags are easy to forget.
- Compressing a video: when a file is too big to email, upload, or attach, I use an online compressor. VideoBee's video compressor handles large single files (up to 10 GB), which is the main reason I use it for files that other tools reject.
- Converting formats: MOV to MP4, MP4 to WebM, and similar jobs are easy to do with a video converter when you don't want to dig up the right FFmpeg command.
- Trimming a clip: cutting the first and last few seconds off a screen recording is a perfect web-tool job. A video cutter does it in the browser.
- For scripting or full control: FFmpeg remains my default. If you want a local GUI, HandBrake is a long-standing open-source option. Audio
- Quick trims and format conversions: a browser-based audio tool is enough for most one-off jobs.
- Real editing: Audacity is the free desktop standard.
- Scripting: FFmpeg again, for extracting or converting audio in bulk. [Add your own picks here, ideally tools you've actually used and can describe in a sentence.]
Images
- Compressing and converting for the web: Squoosh is a browser-based tool that lets you compare formats and quality settings side by side.
- Batch processing: ImageMagick or Sharp (Node) in a script.
PDFs
- Merging, splitting, compressing: browser tools cover the common cases.
- Self-hosted option: if you handle sensitive PDFs, look at open-source tools you can run yourself. [Add the PDF tools you actually use here.]
A small FFmpeg safety net
Even if you prefer web tools, keep these two commands handy for when you're offline or processing many files:
# Compress a video ffmpeg -i input.mp4 -c:v libx264 -crf 26 -preset medium -c:a aac -b:a 128k output.mp4 # Convert MOV to MP4 ffmpeg -i input.mov -c:v libx264 -crf 23 -c:a aac output.mp4 What I don't use web tools for
- Anything confidential, such as unreleased product footage or client documents
- Jobs I'll repeat, since a script pays off quickly
- Very large batches
- Workflows that need to be reproducible in CI
The bottom line
Install software for work you do every day. For everything else, a good browser tool saves time, disk space, and mental overhead.
What's in your no-install toolbox? Drop your favorites in the comments, especially for audio and PDFs, where I'm still looking for better options.
