Frequently asked questions
Common questions about privacy, accuracy, browsers, and how the site works.
Are the tools really free?
Yes. Every tool on this site is free to use, with no account, no paywall, and no usage limit.
Do you upload my files or text?
No. Everything runs in your browser. Files and text never leave your device. You can verify this by opening your browser developer tools, going to the Network tab, and using any tool: no requests fire after the page loads.
Do the tools work offline?
Once a page has loaded, yes. Load the tool, disconnect your network, and it still works. Nothing on a tool page needs a server after the initial page load.
Which browsers are supported?
Any modern browser: Chrome, Edge, Firefox, and Safari, on desktop and mobile. The cryptographic tools use the Web Crypto API, which is available in all of them. Some features - like Ed25519 verification - require a browser from 2023 or later.
Are the tools accurate?
The cryptographic implementations come from established, audited libraries, not hand-rolled code. Where a standard publishes a test vector - SHA-256, AES-GCM, PBKDF2, Argon2, and others - the tools produce the standard output. You can see a live pass/fail table on the verification page.
Is there a CLI equivalent for the tools?
Most pages include a "Command line equivalent" section with the same operation in OpenSSL, Python, Node, or another tool. Open the collapsed section below the main interface to see it.
Can I use the output in commercial work?
Yes. The output of any tool is yours. There is no attribution requirement and no license restriction on the data you compute.
Can I link to a specific tool state?
Yes. On each tool page, the "Share Link" panel under the settings column generates a URL that encodes your input and settings. Copy it and send it. The recipient opens the page and sees the same state.
What happens to my "Remember Input" setting?
If you turn it on, the input for that specific tool is stored in your browser local storage, on your device only. It is never sent anywhere. Turning it off deletes the stored value.
How do I report a bug or request a tool?
Use the contact page. Include the tool name and, if possible, the exact input that produced the problem. Tool requests are welcome; not all of them will be built, but all are read.
Do you use cookies?
The site itself does not set first-party cookies. Third-party services described in the privacy policy do. The site stores your theme choice and "Remember Input" preferences in localStorage, which is not a cookie.
Do you use analytics?
Yes, Google Analytics 4, used to measure page views and see which tools are used. It never sees your tool input. See the privacy policy for details and how to opt out.
Where is the source code?
The site is a static Astro project. The rendered JavaScript of every tool page is inspectable in your browser: open DevTools, go to the Sources tab, and read the tool code directly.
Still have a question?
If your question is not answered here, contact us. Bug reports and tool requests get a real reply.
See also: privacy policy, security and architecture, terms of service.