Where processing happens
Current PDF, image, converter, calculator, text, and QR tool inputs are processed by code running in the browser. The implementations do not send selected files or field values to a Tiny Tiny Tools conversion API. Ordinary page requests and analytics are separate from tool-input processing.
- PDF tools use PDF.js, pdf-lib, fflate, canvas, and browser Blob downloads.
- Image tools use canvas and format-specific browser libraries. Background removal downloads a machine-learning model on first use, then applies it in the browser.
- QR scanning can use an uploaded image or camera frames after permission is granted. Frames are decoded locally and are not automatically opened or submitted.
Temporary data and deletion
Because current tool inputs are not uploaded to an application processing server, there is no server-side conversion file to schedule for deletion. Files and generated object URLs can remain in browser memory until the page is refreshed, closed, or the tool resets them. Downloads remain wherever the user saves them.
Limits and browser memory
Validation limits reduce accidental overload but do not guarantee that every allowed file will fit a device. Large scans, high-resolution photos, multi-page rendering, ZIP creation, and first-run background-removal models can use substantial memory, especially on mobile devices. Keep the original file and close other memory-heavy tabs if processing fails.
How to verify this yourself
Every claim on this page is checkable in about a minute, and checking it does not require taking my word for anything. The counter on each tool page is the short version: it is fed by the browser’s own PerformanceObserver, counts every request the page makes from the moment it finished loading, and includes this site’s analytics. A counter that quietly skipped this site’s own requests would not be worth reading, so it skips none of them — which is why it is not always zero. It is evidence rather than proof: resource timing does not report WebSocket connections, anything a browser extension fetches on your behalf, or requests made before the page finished loading, and no counter can rule out what it cannot observe. That is why the real method is below.
The long version is the browser’s own network panel, which reports what the page did rather than what the page says it did.
- Open DevTools with F12, or ⌘⌥I on a Mac, and pick the Network tab.
- Tick Preserve log so nothing is cleared if the page navigates.
- Use the tool normally — choose a file, run the conversion, download the result.
- Filter by Fetch/XHR to see requests the page made, rather than the scripts, fonts, and images it loaded to render.
- Your file will not appear as an upload. There is no request carrying its bytes, because the conversion ran on your device.
Where the counter is not zero, and why
Two cases raise the number honestly rather than hiding it. Analytics fires on an ordinary page view like any other site’s, and again when a tool first gets input, finishes or fails — so a request to Google appearing the moment you download is that event, which names the tool and not your file. And the background remover downloads its segmentation model and WebAssembly runtime from the model host the first time you use it, which is several requests and the largest download on the site; later runs reuse the cached copy. Your image is not among those requests — the model comes to the image, not the other way round. The panel on that tool says so in place rather than leaving you to work it out from the number.
Sensitive and protected material
Local processing reduces unnecessary file transfer, but it is not a promise that the device, browser, extensions, operating system, or network is secure. Avoid processing confidential, regulated, legally privileged, or irreplaceable material unless you have assessed the full environment. Password-protected PDFs are rejected rather than bypassed.
Third parties used to deliver the site
Vercel hosts the website and may receive normal request information such as IP address, user agent, URL, and timestamps. Google Analytics is currently used for page measurement and for counting whether each tool finished or failed, and is denied storage by default for visitors in the European Economic Area, the United Kingdom, and Switzerland until the consent message on this site is accepted. Advertising is not active anywhere on this site. Tool pages identify important bundled libraries and any additional network download, such as the background-removal model. See the Privacy Policy and Cookie Policy.