The tool I couldn't find, so I built it.

MyFreeInvoiceTool is made by Rob Sawant — an engineer and project manager who spent too many evenings helping friends and family wrestle with "free" web tools that weren't. You know the pattern: you search for a free invoice maker, and twenty minutes later you've created an account, your client list is on someone else's server, and the PDF arrives wearing a watermark you didn't ask for.

Why this exists

At some point, "free" on the web came to mean free to start. Upload your files and we'll hold them. Make three documents, then upgrade. Export with our logo on your work. The basic features are behind a signup, the useful ones behind a card. None of this is necessary — modern browsers are extraordinarily capable, and a tool like this one can do everything locally, on your machine, without a server ever touching your data.

So that became the rule for everything I build: if the browser can do it, the browser should do it. No accounts, because there's nothing to log in to. No watermarks, because your documents are yours. No upsells, because there's no paid tier. And privacy by architecture rather than by promise — your invoices, clients and totals are stored in your own browser and never leave your device. I couldn't look at your data if I wanted to, which is exactly how it should be.

The suite

The same idea now runs across five apps, each free and each processing everything on your device: MyFreePDFEdit for editing, merging and converting PDFs; MyFreeImageTool for image editing, conversion and OCR; MyFreeAudioTool for audio work, right up to a multitrack studio; MyFreeVideoTool for video editing without uploads; and this site, MyFreeInvoiceTool, for invoices, GST billing and every business document in between.

Get in touch

Found a bug, missing a feature, or just want to say the tool saved you a subscription? I read everything. Email me at sawantrob​[at]​gmail.com — replies can take a day or two, but they come from me, not a ticketing system.

One ask: this site can't see your documents (that's the point), so when reporting a bug please mention your browser and what you were doing — it's the only way I can reproduce it.