Local processing describes where work happens
A browser can read a file you select and process it without uploading its contents. That avoids one data-transfer step, but it is not a universal security guarantee. The page still runs software, and browser extensions or a shared device can affect privacy. Check each tool’s stated behaviour. Sending a contact form or publishing a comment is a separate server operation.
Encoding changes representation
Base64 turns bytes into a text representation suitable for certain data formats. Anyone who receives it can decode it; no secret is required. Use it when an API or document format needs encoded bytes, not to hide a password. URL encoding and hexadecimal conversion similarly solve representation problems. A complicated-looking output does not establish confidentiality.
A hash checks a fingerprint
A SHA-256 digest can help compare a downloaded file with a known expected digest. Compute both with the same algorithm and compare every character. A match is useful only when the expected value comes from a trustworthy channel. Hashing is not reversible encryption, and a file hash alone does not identify its author. Do not describe MD5 lookup services as general-purpose decryption.
Encryption needs a complete recoverable package
Encryption uses a key to protect content. A password-based tool also needs a defined derivation method and parameters; authenticated AES-GCM needs a valid unique initialization value for each use of a key. Keep the tool’s complete output, including its format version, salt and other required metadata. Copying only the ciphertext may make recovery impossible. Do a small encrypt-and-decrypt test before relying on the workflow.
Choose according to the job
For a routine image resize, local processing may be the most convenient choice. For file integrity, use a suitable hash and a trusted reference. For confidential content, use a maintained encryption workflow and keep recovery information separate from the protected file. These are different tasks. A useful tool clearly explains its input, output and limits instead of using the word “secure” for everything.
developer.mozilla.org