13 Free Everyday Utilities: Passwords, QR Codes, Timers and Text Encoding
Generate passwords, build QR codes, run timers and clocks, and decode binary, hex and cipher text — all with free browser tools that upload nothing.
ما يغطيه هذا الدليل
- 1. Passwords: the part that actually matters
- 2. QR codes: what to put in them
- 3. Time: timers, clocks and the trap in timezones
- 4. Randomness, honestly
- 5. The encoding junk drawer
- 6. The two that format things
- 7. A worked example: the garbled API response
- 8. Frequently asked questions
- 9. The one-line version
This last group is the junk drawer. Passwords, QR codes, a stopwatch, a world clock, a coin flip, and four tools that convert text into other representations of itself. Individually trivial, collectively the stuff you need at awkward moments.
The through-line is that all thirteen run locally. For a password generator that is not a nicety — it is the entire reason the tool can be trusted at all.
Passwords: the part that actually matters
- Password Generator — generate strong random passwords of any length and character set.
- Password Strength Checker — estimate how resistant a password is to being guessed, locally.
How strength is estimated matters too. Most checkers approximate the size of the search space, which is a reasonable proxy but not the truth: `CorrectHorseBatteryStaple` scores well on entropy, while `P@ssw0rd1!` scores well on character variety and badly in practice because it appears in every cracking wordlist on earth.
Use the generator for anything you care about, and if you have to remember a password, use a passphrase of four or five unrelated words. That is the specific case where memorability and strength actually overlap.
QR codes: what to put in them
- QR Code Generator — generate a QR code for a URL, text, Wi-Fi details or contact information.
QR codes are one of those tools where the output quality is entirely determined by one decision: how much data you put in. A short URL encodes into a small, easily-scannable code. A paragraph of text with punctuation encodes into something dense and unreliable at small sizes.
Two practical rules. First, always test-scan the code at the size it will actually be printed before you print two hundred of them. Second, Wi-Fi and plain URL codes behave differently on different phones — if a code is going to a mixed audience, prefer a plain URL to a landing page that then links onward, because it works everywhere and you can change where it points.
Time: timers, clocks and the trap in timezones
- Online Stopwatch — a plain stopwatch, useful when your phone is in the other room.
- Pomodoro Timer — 25-minute focus blocks with breaks, for people who find that structure works.
- World Clock — current time in several cities at once.
The world clock earns its place for one specific reason: daylight saving. Half the world's scheduling mistakes are not arithmetic errors, they are a moment where two cities were four hours apart last week and five hours apart this week, and nobody checked.
Before scheduling anything across a timezone, put both cities in the world clock and look — do not compute the offset from memory. This is also why meeting invitations should carry a timezone rather than a bare hour.
On the Pomodoro timer: the technique works for a specific kind of task — bounded, focused, uninterrupted. It does not work for debugging, where the correct move when stuck is to walk away, not to start another 25-minute block. Use it when it helps.
Randomness, honestly
The Random Number Generator and the List Randomizer cover the cases that actually come up: picking a number in a range, and putting a list into a fair order. Worth a sentence on fairness. Both use a pseudo-random generator, which for deciding who pays for lunch is indistinguishable from a real coin. For anything consequential — a draw with prizes, an allocation with money attached — you want a source you can audit, and a browser tab is not that. The value here is removing the human, who picks badly when motivated.
The encoding junk drawer
Four tools that move text between representations. None of them are encryption, and the distinction is worth stating because it is constantly confused: an encoding is reversible by anyone and has no key. Encryption requires a key.
- Binary to Text — convert between text and its binary representation.
- Hex to Text — convert between text and hex, the representation you see most often in network tools and debuggers.
- Caesar Cipher — shift letters by a fixed amount, the classic classroom cipher.
- ROT13 Encoder — rotate letters by 13, a special case that is its own inverse.
These are useful for exactly two things. First, understanding how text becomes bytes, which is the mental model you need whenever anything looks garbled. Second, actually debugging: when a payload shows up as hex, the Hex to Text converter is how you find out what it says.
They are not useful for hiding anything. ROT13 has no key — the shift is public — so it hides nothing from anyone who knows what ROT13 is. The Caesar cipher has 25 possible shifts, which a human breaks in minute one.
The two that format things
- Phone Number Formatter — normalise phone numbers into a consistent format.
- File Size Converter — convert between KB, MB, GB and TB, with the decimal and binary distinction explained.
The file size converter has one genuinely valuable output: it tells you why a drive advertises a bigger number than your computer reports. Vendors sell in powers of ten, operating systems report powers of two, and the gap is about 7 percent at every scale. That is not a fault, it is two conventions.
A worked example: the garbled API response
A webhook is failing validation and the payload in the log looks like `\x48\x65\x6c\x6c\x6f`. This is a ninety-second diagnosis.
- 1. Convert. Paste `48656c6c6f` into the Hex to Text converter — the result is `Hello`. It was never garbled, just encoded.
- 2. Check the shape. Something upstream is hex-encoding the payload before signing. The signature was computed over the original text and validated against the hex, so the comparison fails.
- 3. Rule out the other direction. If the log had shown readable text, the problem would have been the reverse: signing the encoded form.
- 4. Confirm the size claim. If the same log reports a 1.2 MB payload, the File Size Converter settles whether that is decimal or binary before anyone argues about a quota.
Frequently asked questions
Is the password generator safe if everything runs in the browser? Yes, and more so than a server-based one: the password is generated on your machine and never transmitted, so there is nothing to intercept, log or breach. The trade-off is that you cannot recover a password you did not save.
Can I trust the virtual coin flip? For casual decisions, yes. For anything with money or prizes attached, use a source you can audit.
Are the ciphers secure? No. None of them. ROT13 and Caesar ciphers have no secret key and exist to teach encoding, not to protect anything.
Do these work offline? Once a page has loaded, yes — everything is local.
Is there a limit on text length for the converters? Only your device's memory, since nothing is sent anywhere.
The one-line version
Long unique passwords beat short clever ones, a QR code is only as good as the data inside it, check timezone offsets rather than computing them, and encoding is not encryption.
جميع الأدوات مجانية وخاصة
تعمل كل أداة مشار إليها في هذا الدليل بالكامل في متصفحك. لا يتم تحميل أي شيء تكتبه أو تلصقه، ولا يلزم وجود حساب، ولا يوجد حد للاستخدام. تصفح صندوق الأدوات الكامل →