About Genfy
Genfy is a small independent project: free online generators that don't waste your time. When you need a strong password, a name idea for a new company, a QR code, or just a decent name for the cat that showed up at your door — you find it here, no pop-ups, no signups, nothing to install.
What we believe
The web is full of "free tools" that hide the actual feature behind a paywall, an email signup, or three layers of pop-ups. Genfy is the opposite of that. Every generator should be instant, clear, and respectful of the person on the other end of the screen. If something feels slower or pushier than it has to, we've broken our own rule.
How does Genfy stay free?
Contextual ads from Google AdSense pay the hosting bill. That lets us keep every tool free with no strings attached. We don't sell your data, there's no hidden "Pro" tier, and the ads are clearly labeled — never disguised as content.
Privacy by design
Most of the generators run entirely in your browser: what you type into them never leaves your device. We don't keep histories of what you generated, we don't build user profiles, and we use cookies only where it actually matters (language preference, consent, ads).
Languages
Genfy is available in English and Spanish today. Each version is written, not machine translated — examples, name lists, and references are adapted to each audience. More languages are coming, but only when we can do them properly.
How we build and test the tools
Every tool follows the same technical rules. The security ones
(passwords, keys, tokens, UUIDs) use the browser's cryptographic randomness
(crypto.getRandomValues / Web Crypto), never Math.random. We
don't fake algorithms: if a tool says it computes a SHA-256 or an HMAC, it computes exactly
that with the standard browser API; if something isn't the real algorithm, we don't call it
by that name. Most generators process your data locally: what you paste
never reaches a server. Before publishing a tool we verify its output against known examples
and test edge cases (empty, very long, special characters).
Accuracy and corrections
Our explanations aim to be correct and verifiable, not just persuasive. If you find an error — a wrong result, a doubtful technical claim or a broken link — tell us from the contact page and we fix it. Each tool shows the real date of its last review, and we only update it when the content actually changed: we don't fake "updated today" on every deploy.
Sources and standards
When a tool implements a standard, we follow its official specification: UUID and JWT per their RFCs, SHA hashes per FIPS, the contrast checker per WCAG 2.1, and the data formats (JSON, YAML, CSV, XML) per their specs. To understand the differences between similar options we write comparisons, and to finish whole tasks we chain tools into workflows.
Get in touch
Found a bug, want to suggest a generator, or just want to say hi? Drop us a line from the contact page.