Making everyday web tools fast, simple, and private.
A collection of 70+ free browser-based utilities built and maintained by one person who cares about your privacy.
Why I built SwiftTooly
I was frustrated uploading private PDFs and photos to random websites just to do simple tasks — merge a document, compress an image, convert a file. I never knew where those files ended up, who had access to them, or what trackers were running in the background.
So I built SwiftTooly: a toolbox where everything runs in your browser and nothing is ever uploaded to a server. No accounts, no permissions, no catch. Just open a tool, get your work done, and move on.
I care about making things that feel effortless. Every tool here is designed to load fast, work smoothly, and respect your time.
What makes it different
SwiftTooly is built on a few simple principles I believe in deeply.
100% Browser-Based
Files and data never leave your device. Every conversion, edit, and calculation happens locally in your browser.
No Sign-Up Required
Open a tool, use it, close it. No accounts, no newsletters, no friction. It just works.
Privacy where it counts
Your files and everything you type never leave your device — all processing happens in your browser. We use basic, privacy-respecting analytics only to see which tools are used most, never tied to you personally.
Free Forever
Built to be genuinely useful, not to upsell you. Every feature is free and will stay that way.
Who I am
I'm Ahmed Kobbi, an indie maker who builds and maintains SwiftTooly. I design, code, and ship every part of this site myself — from the tools to the copy to the design.
I started this project because I believe small utility tools should be fast, trustworthy, and free. No corporate team, no investors, no growth-hacking — just one person trying to make the web a little more useful.
Want to say hello or suggest a tool? Get in touch.
How “no upload” actually works
Every file tool here runs as JavaScript inside your browser tab. PDFs are parsed and written with pdf-lib and rendered with pdf.js. Images are decoded and re-encoded through the Canvas API. Passwords and UUIDs come from the Web Crypto API, which draws on your operating system’s own entropy pool. QR codes are generated locally and encoded directly into the image.
None of those steps involves a network request carrying your data. There is no upload endpoint, no processing queue and no temporary storage, because there is nothing on our side to store anything in. That is an architectural property rather than a policy commitment — the difference being that a policy can change with a document revision, and an architecture cannot.
You do not have to take my word for it, and you shouldn’t. Open your browser’s developer tools, switch to the Network tab, and use any tool on the site: no request carrying your file appears. Or run the simpler test — load a tool page, disconnect from the internet, and use it anyway. It still works, which would be impossible if your file were being sent somewhere.
The honest limits are worth stating too. Anything that fetches external data needs a connection — the YouTube thumbnail downloader has to request the image from YouTube’s servers, though the URL is parsed locally and never reaches us. There is no OCR, because text recognition needs models far larger than a browser should download. And because your device does the work, a very large job on an old phone will be slower than a server would be.
I use privacy-respecting analytics to see which tools get used, so I know what to improve. That records page views, not content: nothing you type, paste, upload or generate is ever part of it. The privacy policy sets out exactly what is and is not collected, and the guides go into more detail on how to verify any tool’s behaviour for yourself.
Ready to try a tool?
Explore all tools