Guides
Why AyukTools processes files in the browser
What client-side tools actually do, which jobs still leave your device, and why that design exists on a small utility site.
Written by the AyukTools team · 2026-09-10
A file does not have to travel to be useful
A QR pattern, a PDF page, or a photo resize is math on pixels and bytes. Modern browsers can do that math in a tab. Sending the original to a server would only add a queue, an account, and a copy of a document you may not want sitting on someone else’s disk.
AyukTools is built around that idea. Generate a QR, scan one, convert PDF pages, merge images into a PDF, convert or compress a picture, or crop a video clip: the original stays on the device unless you download a new file yourself. Closing the tab clears the working copy.
What still leaves the device, on purpose
An internet speed test cannot stay fully local. Measuring download, upload, ping, and jitter means talking to a machine on the public internet. This site uses Cloudflare for that burst. The numbers are a snapshot of a route, not a file you uploaded.
Optional AI on the vertical clipper is the other exception. If you paste a Gemini key and a public YouTube URL for a video you published, that request goes to Google so the model can suggest times and captions. AyukTools does not keep the key or a history of analyses.
Why this matters for everyday work
School forms, shop menus, and invoices often contain names, addresses, or prices. A tool that asks you to upload first treats that as normal. A tool that runs in the tab treats it as avoidable. You still choose what to download and where to send it next.
Local processing is not magic privacy. A screenshot, a shared computer, or an extension can still see the tab. It does mean this site does not need a file database to do the job, which is the promise on the About and Privacy pages.
How to tell which kind of page you are on
Each live tool has a short privacy note under the widget. Read that before you pick a sensitive file. If the page says the work stays in the browser, it should not ask you to create an account to finish.
If a future tool must talk to a third party, the page should say so in the same place. The speed test and the optional Gemini step are the current examples. We do not hide those hops behind a generic “upload” button.