Frequently Asked Questions

No. Most tools work instantly without any account.

Many tools are fully client-side; once loaded, they continue to work offline. A future PWA update will improve offline caching and “Install app” support.

Yes—everything is built mobile-first and tested on common screen sizes.

The interface is English for now. We plan to add localized UI strings later.

Client-side randomization uses the browser’s Math.random() (non-cryptographic). It’s fine for everyday picks. For security needs, use the Password Generator (cryptographically strong) or a server-side RNG.

Yes—choose words, sentences, or paragraphs and copy to clipboard. Advanced options (headings, lists) may be added later.

Yes—the generator runs in your browser and can export PNG/SVG without uploading the content to our servers.

Limits depend on your device memory and browser. For very large images, use a desktop editor or process in batches.

It checks text/background color contrast against common accessibility guidelines (AA/AAA thresholds) and includes guidance for small vs large text.

They run locally in your browser. Do not paste secrets you wouldn’t paste into any website. For sensitive workloads, prefer offline/CLI tools.

Most tools are client-side and inputs aren’t sent to our servers. If a tool needs a request (e.g., IP lookup), we’ll say so on that tool page.

Image tools process files locally in your browser using Canvas/Web APIs. Files aren’t uploaded unless explicitly stated.

We may store lightweight preferences (like dark mode) in localStorage. Any analytics cookies will be disclosed in the Privacy Policy.

We may use privacy-respecting analytics to understand feature usage. Personal data isn’t required to use the tools.

For client-side tools, nothing is retained. For contact forms or feedback, we keep messages as needed to respond and maintain service quality.

Latest Chrome, Edge, Firefox, and Safari. If something looks off, update your browser or try another engine.

Mobile-first UI, minimal JS on heavy pages, and client-side processing where possible to reduce network latency.

PWA support is planned. You’ll be able to “Install” from the browser menu for quick access and better offline use.

Common actions (copy, clear, generate) are keyboard friendly. We’ll document per-tool shortcuts on each tool page.

Files you export (e.g., images, QR codes) will be saved to your browser’s default download location unless you change it.

Refresh the page, try another browser, then report the issue with steps to reproduce via the contact form.

Linking is encouraged. Basic iframe embedding is allowed for non-commercial educational use with attribution. For commercial or high-traffic embedding, please contact us.

Yes, within fair use. Avoid automated scraping or republishing our UI as your own product. Contact us if unsure.

Linking back is appreciated but not mandatory for regular use. For embedding or reproducing content, attribution is required.

Educational use is welcome. If you plan classroom-wide or lab deployments, reach out so we can help with setup guidance.

Avoid pasting secrets into websites. Use offline/CLI tools for confidential material. Our tools run locally where possible, but caution is best.

Email us via the contact page. Please include steps to reproduce.

Normal human use is fine. Automated scraping or abusive traffic may be blocked to protect the service.

Use the contact form with steps, screenshots, and your browser/version.

Submit a feature request describing the problem you want to solve and any similar tools you like.

We usually reply within 24–48 hours on business days. Complex requests may take longer.

Not yet. We’re focused on great in-browser tools first. If we add an API, we’ll announce it on the homepage and Tools page.

We may open-source select tools or libraries in the future. Keep an eye on our GitHub link in the footer.