Listen to this post: The Vibeland Tools That Need a Server, and Why
Almost everything on Vibeland runs on your own machine. Paste text into the JSON formatter or a token into the JWT decoder and nothing is transmitted — the JavaScript executes in your browser, and both would keep working with the network switched off.
A handful of tools cannot work that way. Rather than blur the distinction, the site groups them and says so. This post is about that group: what is in it, why those particular jobs need a server, and what it means for what you should put into them.
The four that genuinely can’t run locally
The site is specific about this. OCR, background removal, PDF extraction and certificate checks cannot run in a browser tab. Here is why each one is on that list.
OCR
Optical character recognition — reading text out of an image — depends on trained models. Useful accuracy across varied fonts, handwriting, skewed photos and poor lighting takes a model far heavier than anything you would want to download into a tab before it will do anything.
Browser-based OCR does exist, and it is fine for clean, high-contrast, printed text. It degrades quickly on a photographed receipt or a screenshot of a console. The tradeoff is real and it points to a server.
Background removal
Separating a subject from its background is a segmentation problem. Doing it well — hair, soft edges, a busy background — is model work, and the same weight argument applies.
PDF extraction
Pulling structured content out of a PDF is harder than it sounds. A PDF describes where marks go on a page, not what the text means. Reconstructing reading order from a two-column layout, or getting a table out with its rows intact, takes machinery that a lightweight client-side parser will not match.
Certificate checks
Checking an SSL certificate is on the list for a completely different reason. It is not about weight — it is that the check has to actually connect to the host and inspect what it is serving. Your browser cannot open an arbitrary connection to someone else’s server to examine their certificate chain; that is precisely the sort of thing browser security prevents. Something has to make the request from outside your tab.
The rest of the category
The same category also holds IP geolocation, which looks an address up against a database, and the meta scraper, which fetches a page and reports its title, description and Open Graph tags — genuinely useful for checking how a URL will preview before you post it somewhere.
Alongside those sit the QR generator, the password generator and a validation tool.
What this means for what you paste
The practical value of the distinction is that it lets you make an informed decision instead of a hopeful one.
For the client-side majority — the text tools, the encoders, the data converters, the generators, the calculators — the question of trust barely arises. Nothing leaves your device, so there is nothing to trust with.
For the server-backed handful, ordinary judgement applies, and it applies to every online tool of this kind rather than to this one in particular:
- A screenshot of a public webpage through OCR — no real issue.
- A product photo through background removal — no real issue.
- A signed client contract, a medical letter, or a document under NDA through any online extractor — think about it first, and if the answer matters, use something running on hardware you control.
That is not a warning about this site specifically. It is the reasoning any competent person applies before uploading a confidential document anywhere, and it only works if you know which tools upload and which do not.
Why the distinction is worth making at all
Plenty of tool sites market themselves on privacy while quietly routing everything through a backend, because “your data never leaves your browser” is a good line and nobody checks. Others do the reverse and never mention it either way.
Stating which tools run where is a small thing, but it is the difference between a claim you have to take on faith and one you can verify — open the network tab and watch whether a request goes out. For the client-side tools, it does not.
The full set is at vibeland.co.uk/tools: 117 tools, 17 categories, no account, no limits.
