Browser-based tools vs cloud tools: when to use which

We're obviously biased — this site is built around browser-based tools. But cloud-based tools aren't bad, they're just different. Here's an honest comparison so you can pick the right one for the job at hand.

Speed

Browser tools win on small files. No upload time, no queue wait. A 5 MB PDF merges in under a second on a modern laptop. You click "Merge" and the file is downloading before your eyes refocus.

Cloud tools win on big workloads. Compressing a thousand images, OCR-ing a long document, or running an AI model that needs a GPU — all of these are 10-100× faster on dedicated cloud hardware than on your laptop. If you're processing a single 50-page PDF, the browser is faster. If you're processing five thousand, the cloud is.

Privacy

Browser tools win, period. Your file never leaves your device. Even the most trustworthy cloud operator has logs, has a privacy policy you have to read, has a security incident in their future. Browser tools have none of these because they have no server-side state.

Cloud tools' privacy is as good as their operator. Some are excellent. Some are awful. The trouble is you can't easily tell which from the marketing page.

Capability

Cloud tools win on heavyweight features. OCR with high accuracy, document understanding, GPU-bound transformations, large language model inference, video transcoding — these need real compute and persistent state that's hard to replicate in a browser tab.

Browser tools have caught up on most everyday workflows. PDF editing, image manipulation, format conversion, hashing, encoding — all routine in the browser today. WebAssembly + Canvas + SubtleCrypto cover a surprising amount of ground.

Cost

Browser tools are free to operate. No per-request server cost, no queue infrastructure, no scaling worries. We can keep the tools free indefinitely because there's nothing to scale.

Cloud tools have real per-use costs. Even free tiers have caps because somebody is paying for the compute. The economics force eventual paywalls or aggressive ads.

Reliability

Browser tools have one dependency: the user's browser. If the page loads, it works — even with no internet connection (after the first visit, since the JavaScript caches).

Cloud tools depend on the operator's uptime. If their server is down, you're stuck. Most have good uptime, but "the tool stopped working at 3am Sunday" is a class of problem we don't have.

Sharing & collaboration

Cloud tools win. Multi-user editing, comments, shared links — all need a server.

Browser tools are inherently single-player. Each session is independent. We don't try to compete here.

When to pick browser-based

• One-off file work — merging a few PDFs, compressing some screenshots
• Sensitive content — anything with PII, financial data, or under NDA
• Quick utilities — JSON formatting, hash generation, text diff
• Offline work — flights, conferences, anywhere the network is unreliable
• "I just want it done now" tasks where signup friction would kill it

When to pick cloud-based

• Recurring batch jobs — automated workflows, integrations, scheduled processing
• Heavy ML — transcription, translation, generative models
• Multi-user collaboration — shared documents, shared review
• Persistent storage — versioning, history, asset libraries
• Strict latency for users without good devices

A reasonable hybrid

The best workflow for most teams is: cloud for the platform of record (Google Drive, Notion, Dropbox), browser-based for the ad-hoc transformations. Keep your master files in the cloud, but when you need to compress a screenshot before pasting it into Slack, do that locally — there's no reason to round-trip the bytes through a third party for a 10-second job.

The two approaches aren't competing. They're solving slightly different problems, and the rise of capable browser-based tools has just given us a much better default for the everyday stuff.