Guide
Browser-only Tools vs Server-processed Tools
Understand when a utility can run locally in your browser and when server-side processing is needed for heavier workflows.
Start with the processing location
A browser-only tool reads input in the current tab and performs the task with JavaScript or browser APIs. A server-processed tool uploads content temporarily so background infrastructure can complete heavier work. Knowing the processing location helps you choose the right workflow for sensitive or large files.
Use browser-only tools for quick inspection
Formatting JSON, cleaning a small CSV, generating a QR code, testing a regex, converting timestamps, and hashing a local file can usually happen without sending content to a server. These tasks are good candidates for local processing because they are fast and do not require specialized backend workers.
Use server processing when computation is heavy
Speech-to-text transcription, large OCR jobs, and some media conversions require more CPU, memory, or specialized software than a browser tab can reliably provide. In those cases, check upload limits, retention windows, and deletion rules before starting.
Match the risk to the task
A public sample file, a copied code snippet, and a confidential contract do not carry the same risk. For private work, use the smallest necessary input, remove fields you do not need, and prefer local processing when it can produce the result.
Review outputs before sharing
Local processing reduces transfer, but the output can still reveal private information. Extracted text, formatted JSON, decoded strings, and metadata should be reviewed before being pasted into tickets, emails, or public documents.