MTC Lab

Making things

keeplocal

File tools that never upload your file. Merging a few PDFs, resizing an image, stripping the GPS coordinates out of a photo before you send it - the ordinary jobs that the big online tools take your file for, and then paywall or ad-gate. keeplocal does the work inside your browser instead, so the file physically never leaves your machine.

What it is

Five tools, each on its own address. PDF tools count, merge, organise and compress. Image tools resize, convert and compress, and strip EXIF and GPS data. The metadata scrubber shows you what is hidden inside a file - location, camera, author, editing history - and then removes it. The archive tool zips files up or opens a zip and pulls files out. Images to PDF combines JPG and PNG files into one document, reordered and stripped of EXIF and GPS on the way.

Each one runs its file logic in Rust compiled to WebAssembly, inside your browser, in a worker thread. There is no upload because there is no server to upload to.

Why you can check it rather than believe it

The promise is only worth something if it is verifiable, so every surface prints a receipt taken in your own browser at that moment: how many external requests the page has made, what its connection policy is, whether any third-party script is present, how many cookies were set. Open your network panel and check the numbers yourself. Every tool ships a strict policy that permits connections only back to its own static origin, so the page could not send your file elsewhere even if it tried, and the tools keep working with the network unplugged. The whole thing is open source under the MIT licence, so the claim can be read in the code.

There is a second kind of honesty in it. Some things a tool does to a file cannot be seen in the file afterwards: an animation flattened to a single frame, colour depth rounded down, or a document handed back untouched because compressing it would have made it worse. All of those look like success from the outside. So the engine returns notices written for the reader alongside the bytes, and the interface has to show them; the two cases that mean the advertised work did not happen to the file you just downloaded are escalated rather than tucked away.

What it does not do

No upload, no account, no email address, no advertising, no analytics, no cookies. The only thing kept in your browser is whether you chose the light or the dark theme. Nothing is stored for you, which also means nothing is stored about you.

Where it stands

Live, free and open source. Five tools running today, MIT licensed, with the source at github.com/mtclab/localbench - localbench is the engine's repository name, keeplocal is the product.

keeplocal.toolsThe front page runs the same receipt as the tools do, before you have opened a single file.

Elsewhere: vahti·Vigla·Asuntodata·Gamecove·Facet·Forge·keeplocal