45 tools · runs in your browser

free tools. zero friction.

Most online tool sites upload your files to a stranger's server and call it “free.” We do not. Every tool here runs locally in your tab — no upload, no account, no aftertaste.

Privacy as architecture

Your files never leave the tab

Most tools here use no server at all. The ones that do (link checks, OG previews) only handle URLs — never your files.

No accounts. Ever.

Open, use, close

We do not ask for your email, build a profile, or remember you between visits. There is nothing to log into.

Free, on purpose

Funded by ads, not your data

A small ad pays for hosting. We do not sell anything, upsell anything, or watermark anything to make you upgrade.

Popular tools

The ones people open most often.

See all →

From the blog

Notes from the team — engineering, design, the occasional opinion.

All posts →

Why this site looks the way it does

Every couple of weeks, you need a small thing done. Merge two PDFs. Compress a screenshot before emailing it. Pull the colors out of an image. Format an unholy block of JSON. The default way to handle this is to type the problem into Google, click the first result, drag your file in, and hope.

What that file does next is mostly invisible to you. It uploads to a server somewhere. It gets processed. It might get deleted in an hour, or it might get retained for analytics, or it might get fed into an ad network's profile-building pipeline. You took the operator at their word, because there was no other option.

Persimmon is the version of those tools that decided not to move your file at all. The PDF tools, the image tools, the text tools — almost everything here runs entirely inside the browser tab you have open. The byte stream of your document does not cross a network boundary, because there is no network call to make. We could not see your file if we wanted to.

That decision shaped what we will and will not build. We do not have OCR yet, because the practical client-side options are slow. We do not have document templates, because templates need persistence and persistence needs accounts. We are fine with those trade-offs, because the alternative is the model we specifically did not want to repeat.

The blog has more on the engineering decisions behind individual tools — the privacy model behind the PDF tooling, the math behind the contrast checker, why we picked v4 UUIDs as the default for the ID generator. If you want the long version, it is over here.

Something wrong?