Toolspike is a collection of 49 small utilities for everyday files, grouped into 10 categories: PDFs, images, converters, developer utilities, mathematical notation, spreadsheets, recognition and OCR, translation and calculators. Each one does a single job, opens immediately and has a free trial every day, with no account needed.
40 of them work today and run on your own device. 9 depend on an external provider and stay switched off, and labelled as such, until that provider is configured.
The tools exist because the alternative is usually an advertisement-heavy page that asks you to upload a document you would rather not hand over. The file tools here run in your browser instead.
Three engineering principles
These are the decisions that shape everything else, including the things Toolspike cannot do.
Local-first processing
Every PDF, image, spreadsheet, data and LaTeX tool reads your file with the browser File API, works on the bytes in the tab, and returns the result as a download. Those tools have no upload endpoint, so file contents are never transmitted, queued or stored.
This is an architectural property rather than a promise. Open the Network panel in your developer tools and run a conversion: you will see the page assets, the library that tool needs and a small request that sends only the tool’s name to check your free run, and no request carrying your document. Disconnecting from the network after the page has loaded is an even blunter test — the local tools keep working.
The recognition and translation tools are the stated exception. They cannot run locally, so they send your input to a configured provider. Every one of them says so on its own page and in the catalogue before you give it a file.
Heavy libraries load on demand
Running real work in the browser means shipping real code. A PDF renderer, a spreadsheet parser and a LaTeX typesetting engine are each far larger than a page of HTML, and bundling all of them together would penalise everyone who only wanted to format some JSON.
Each tool therefore imports its dependencies dynamically, at the moment you open it. Browsing the catalogue costs nothing beyond the page itself. Opening the LaTeX editor fetches the typesetting engine; opening the QR code generator does not. After the first fetch, the browser caches the module for later visits.
Keyboard and accessibility as a baseline
Accessibility is treated as part of the build rather than a later pass. Every control has a visible label, focus is always visible, interactive targets are at least 44 pixels tall, and colour is never the only way information is conveyed.
Search is reachable from anywhere by pressing the / key, results move under the arrow keys, and Enter opens the highlighted tool. Long-running operations announce their state through live regions so that progress is not communicated by a spinner alone.
The colour tokens used across the site are chosen to meet WCAG AA contrast in both light and dark themes, including form controls and borders, which contrast checks aimed only at text tend to miss.
What Toolspike is not
Stated plainly, so you can decide quickly whether this is the wrong tool for your problem.
It is not cloud storage
No file is saved between visits, and an account changes nothing about that: there is no file history, no shareable result link and no way to resume a job on a different device. That is the direct consequence of processing locally, not an omission we intend to fix.
There is no API yet
Toolspike is a set of interactive pages. There is no public HTTP API, no CLI and no way to automate a conversion from a script. An API would require running the work on a server, which would undo the property the tools exist for.
Large files are bounded by browser memory
A server can stream a very large document through a fixed buffer. A browser tab generally cannot: the file has to fit in memory alongside the working copy. The ceiling depends on your device, browser and open tabs, so we describe it as a real constraint rather than quoting a size we cannot guarantee.
Some conversions are out of reach
A few transformations genuinely depend on large native toolchains, wide font libraries or licensed codecs that are impractical to ship to a browser. Where that applies, the tool is absent rather than quietly uploading your file somewhere.
Who runs this
Toolspike is built and maintained by Rahul B, an independent developer based in Pune, Maharashtra, India. It is a personal project rather than a company, which is why the writing says “we” out of habit but there is only one person behind it.
That is deliberate: every tool here was written because an existing one was slow, covered in advertising, or wanted a file uploaded that had no business leaving the machine it was on.
I also run CalcCopilot, a separate site of free finance, health and everyday calculators. A few tool pages here point to one of its calculators when it covers the next step of the same job.
Email reaches me directly at [email protected]. Bug reports and corrections are genuinely welcome.
How it is paid for
There is no advertising on this site and there never will be. No ad network, no ad slot, no tracking script paying for the hosting bill.
Instead it runs on credits for use beyond each tool's free daily trial, affiliate commissions from labelled links, and occasional paid placements that are marked as paid. None of those affect what a tool does or what it tells you, and every tool keeps a free trial each day.
The disclosures page sets out exactly what is paid for and what is not.