How tools work

Browser tools

Developer and text tools process input in the browser. Many PDF and image tools attempt browser processing, while some workflows use server processing or a server fallback. Browser file tools use JavaScript and local libraries to create downloads. Some file workflows use a server fallback when local processing fails; only submit a file you are comfortable sending to the service. You can retain the original and review or discard the downloaded copy.

Opening a page still makes ordinary website requests for HTML, scripts, fonts, and other assets. Website analytics and operational logs are separate from tool contents. “Browser processing” describes the working input, not an offline website or an absence of all network traffic.

Server-side network lookups

IP Lookup and DNS Lookup submit the address or domain you enter to server-side lookup infrastructure. Results can involve external data providers and caching. Use public targets and do not submit internal hostnames or personal identifiers. An approximate location does not identify an individual.

Output limitations

Page-copying PDF operations can change document-level forms, bookmarks, attachments, or signatures. Image exports can change metadata, color handling, animation, and transparency. Text conversions depend on encoding and counting rules. Review the individual tool guide for the behavior that matters to your task.

Capacity and compatibility

Large files and complex documents can exhaust browser memory. File size alone does not predict processing cost: a heavily scanned PDF or a very large image can require much more memory after decoding. A current browser, a smaller test input, and closing other heavy tabs can help. Unsupported or encrypted inputs may still require another application.

Feedback and updates

If a documented example gives a different result, report the issue with an invented, non-sensitive sample. We do not publish a claim that every file, format, or device will work.