About ToolBirch
152 free tools across 13 categories, each doing its work on your device instead of on a server.
Why local processing
Most online tools ask you to upload a file or paste a document, wait for a server, then collect the result. That round trip adds latency, puts a size limit on your work, and sends your data through someone else's infrastructure. For the work ToolBirch does, none of that is necessary: modern browsers can decode images, draw to a canvas, manipulate PDFs and run plain JavaScript on their own.
ToolBirch uses those browser APIs directly. HEIC decoding uses a WebAssembly build of libheif loaded on demand, and PDF work uses a JavaScript library bundled with the page. Everything else relies on native browser capabilities. Your files and text stay in the tab and are handed back as a download or a copyable result.
What we deliberately left out
There is no account system, no upload endpoint, no database and no server-side processing pipeline. Analytics and verified site ownership are optional and switched off until configured. Ad slots exist as reserved space in the layout but are disabled by default and never overlap the tool controls.
Anything the browser cannot do reliably is not offered as a fake option. Where a tool has a real constraint — for example a browser encoder that only supports lossy output — the interface says so and offers a working alternative instead of silently producing the wrong result.
How tools are organised
A single registry defines every tool's route, category, metadata, input rules, UI component and, where applicable, its processor. Sitemaps, navigation, breadcrumbs, internal links and metadata are all generated from it, so a tool cannot silently end up with a missing page or a duplicated description. Tools can be disabled, reordered or recategorised in that one file. A category is only published once it contains at least one real tool.
Get started
Open the tool directory and pick a tool. If you want the details on what data the site handles, read the privacy policy.