Every free versus paid comparison eventually becomes a list of feature checkboxes. We run one of the free sides of that comparison, this site, and the interesting facts are not feature rows. They are the engineering tradeoffs we accepted and the concrete price we already paid for the model. Here is what a no-account, browser-only tool site actually gives up, measured from our own code.
What Browser-Only Actually Means Here
WebRecast ships as a static build. The package scripts are vite dev, vite build, and vite preview, with no server component at all. We searched every file in the components directory for network calls and found zero. Tool pages do not upload your input anywhere because there is nowhere to upload it.
The image compressor shows the pattern. It runs the browser-image-compression library with useWebWorker true, so the heavy work happens off the main thread. It caps processing at a 10 MB input option and a 4096 pixel maximum dimension. Your quality setting, default 80, persists in localStorage under the key img-compress-quality, not in an account on our side.
How the Free Model Pays for Itself
The site is funded by advertising. Our ads.txt authorizes exactly one seller, google.com with publisher ID pub-2046612602451922, sold DIRECT. There is no subscription tier, no account system, and no payment flow anywhere in the codebase.
Honest status: the ad slots currently render nothing. The AdSlot component defines side, infeed, and inarticle formats and returns null today. Revenue depends on ad approval actually being in effect, so the free model here is free in a literal sense right now, and its funding path is a plan rather than a running paycheck.
What Ad Dependency Already Cost Us
This is the part free versus paid articles never quote, because sites do not publish their rejections. Our project guidelines record that AdSense rejected the site for low-value content. The engineering response is visible in the code and it was expensive.
The sitemap generator now includes English URLs only, about 1,424 of them, down from 19,950 across all language versions. A separate component applies noindex,follow to every non-English page, 13 of our 14 supported languages. The reasoning sits in the code comments: thin multilingual duplicates were the risk. The free model shows ads, and holding on to the ad network cost us most of our search footprint. A paid product funded by subscriptions would never make that trade.
What You Give Up With No Accounts
The account-free design has costs on your side of the screen.
- No sync. Favorites live in localStorage under wr-favorites and compressor settings under img-compress-quality. Clear site data, switch browsers, or move machines, and both are gone.
- No collaboration. Two people cannot share a tool session, because nothing about a session leaves your browser.
- No history. There is no server remembering your last calculation or your last ten compressed images.
- Size ceilings. Browser memory and the 10 MB option cap bound what client-side processing can handle, where a desktop tool would stream larger files.
When Paid Tools Win
State these plainly, because the free model loses them.
1. Team workflows. Real-time multi-user editing needs a backend with sessions and conflict resolution. A static site cannot offer it.
2. Batch processing at scale. Hundreds of files in a monitored pipeline need a queue, and queues need servers.
3. Support obligations. If a missed deadline costs you money, you need a support contract, and free tools carry none.
4. Cross-device continuity. Accounts exist so your work follows you. Without them, your browser is your only copy.
Decision Rules
1. If your input is private or sensitive, use a client-side tool and confirm it makes no network requests, ours passes that check by construction.
2. If the task takes under ten minutes and happens occasionally, use a free browser tool, installing and subscribing both cost more than the task.
3. If output must sync across people or devices, pay for a product with accounts.
4. If a subscription you already pay covers the task, use it before adding another free tool to your routine.
5. If a free tool carries ads you cannot accept, pay for an ad-free alternative, that is a legitimate preference, not a luxury.
Checklist
- [ ] You confirmed the tool processes files locally before uploading anything sensitive.
- [ ] You exported or noted settings you care about, they live only in this browser.
- [ ] You chose paid tooling for anything with team or support obligations.
- [ ] You accepted the size ceilings of browser processing for your largest files.
- [ ] You understood the ad-supported tradeoff, including what it did to our own reach.
See the model in practice on the [image compressor page](/en/image-compressor), where compression runs in a web worker and no file leaves your machine. If you have measured a case where the free path or the paid path clearly won, send us the numbers and we will add them here.
