The things people ask most often about the tools and how they handle files.
No. There is no sign-up, no login and no email required. Open a tool and use it.
Yes, including for commercial work. The site is funded by advertising, and there is no premium tier that unlocks features, removes watermarks or lifts a limit. Nothing produced here carries a watermark.
No fixed limit. Because processing happens on your own device rather than on a server, there is no bandwidth cost to control. The practical ceiling is your device's available memory — a laptop handles very large files comfortably, an older phone less so.
Partly. Once a page has loaded, most tools keep working without a connection because all the processing is local. The exceptions are the QR generator and the PDF tools, which load a code library from a content delivery network when the page first opens.
Any current version of Chrome, Firefox, Safari or Edge, on desktop and mobile. A few output formats depend on browser support — AVIF encoding, for instance, is unavailable in some older versions, and the tool will report an error rather than fail silently.
No. Every tool runs inside your browser. Files are read into memory, processed by code running on your device, and saved straight back to your device. Nothing is transmitted, which is why there is no upload progress bar and no waiting.
Open your browser's developer tools, switch to the Network tab, and use any tool on the site. You will see the page and its libraries load, and then no further activity while your file is processed.
We cannot. The file contents never reach us, so there is nothing to store, log, retain or hand over. This applies equally to text you type into the word counter or JSON formatter, and to passwords generated by the password tool.
From our side, yes — contracts, medical records, identity documents and files containing API keys are all processed locally. The usual caution about your own device still applies: anyone with access to your computer can see what you are working on.
PNG is a lossless format, so quality settings have little effect on it. Converting a compressed JPG into PNG re-encodes it without any lossy saving and usually increases size. For photographs, choose WebP or JPG.
WebP is the sensible default — typically 25 to 35 percent smaller than JPG at the same visual quality, and supported everywhere current. AVIF is smaller still but slower to encode. Keep PNG only for logos, screenshots and anything needing transparency.
Browsers cannot decode HEIC natively. Either change your iPhone to capture in JPG — Settings, Camera, Formats, Most Compatible — or convert the photos before using them here.
Yes. Re-encoding through the browser's canvas strips metadata including camera model, timestamp and GPS coordinates. This is useful before publishing photos, and worth knowing if you needed that metadata preserved.
The most common cause is password protection. A file requiring a password to open cannot be read without it, so remove the protection in the application you own the file with, then try again. A damaged or truncated file will also fail.
Merging does not compress. The output is roughly the sum of the inputs, because pages are copied rather than rebuilt. If the result needs to be emailed, compress the individual files before merging — most of the weight in a large PDF is scanned images.
No. Merging and splitting produce a new document, which invalidates digital signatures and drops form fields and annotations. Keep the signed originals; treat the merged copy as a convenience copy only.
Not if the pages are images. Making scanned text searchable requires OCR, which is a separate process and not something these tools perform.
No tool can promise that. This one handles dimensions and head positioning to published specifications. Acceptance also depends on lighting, expression, sharpness and background uniformity, all judged by the issuing authority. Check their official guidance, and use a professional service when an application is time-critical.
No. The background colour applies only where the photo does not fill the frame. Automatic background removal leaves edge artefacts around hair that authorities frequently reject — retaking the photo against a plain light wall gives a far better result.
Advertising, through Google AdSense. That is the entire model. There is no data to sell, since files never reach us, and no premium plan to upsell.
Yes, and specific suggestions are the useful ones. Describing the actual problem — and what you currently do instead — says more than naming a feature. The contact page has the details.
Email the details described on the contact page. Since nothing is uploaded there are no server logs to inspect, so a description of the file and the steps you took is more useful than the file itself — and safer for you.