1.What this site is
tooldura is a collection of 18 small utilities across 8 categories: counting words, formatting JSON, generating passwords, converting units, checking how a page title will look in search results. Each one does a single job and asks nothing of you before it works.
2.Everything runs in your browser
Every tool here is JavaScript that executes on your device. Text you paste into the word counter, JSON you format, images you round the corners of, passwords you generate: none of it is sent to a server, because none of the tools have a server side to send it to. Whatever you type stays in the tab until you close it.
- No file uploads, so your documents and images never leave your machine
- No accounts, so there is nothing to breach and nothing to delete
- Once a page has loaded, its tool keeps working with the network disconnected
- Open the Network tab while using a tool: nothing you typed is sent anywhere
3.Where the numbers come from
Getting a number roughly right is easy. Getting it right at the edges means reading the specification. The length converter works from defined ratios, so an inch is exactly 25.4 millimetres and not a rounded decimal. The social counter weights characters the way X does and bills every link at 23, whatever its real length. The meta length checker measures rendered pixels, because search results are cut on width rather than on a character count. The password generator draws from the browser's cryptographic randomness, never from Math.random. Where a published standard exists, the tool follows it.
4.What gets built next
There are 18 tools here rather than two hundred, and every one of them works. A tool goes up when it does its job properly, not when a category looks empty, so nothing on this site is a placeholder for something planned. You will not find a link that leads to a "coming soon" notice, and no category is padded out with tools that do not exist yet. New ones arrive when they are worth using.
5.Why the guides exist
Every tool on tooldura has a written guide behind it, and those guides exist because the tools raise questions the interface cannot answer. Why two word counters disagree. Why an emoji costs two characters. Why MD5 is broken for security but fine for checksums. The guides are written from primary sources and standards documents rather than summarised from other blogs, and each one names the specifications, studies, or incidents it draws on.
6.Corrections and requests
If something here is wrong, tell us and it gets fixed. Technical writing ages, platform limits change, and standards get revised. Corrections, bug reports, and suggestions for new tools all go to devalex019@gmail.com, and every message is read.