Word tools

Not every problem on this site is a file. This family is for words themselves — turning a scrambled rack of letters into every real word it can make, working out which of those words is worth the most once a board and its premium squares are involved, and reading the coloured clues of a five-letter guessing game back into the answers they still permit.

3 tools

  • Scrabble Word Finder — The Best Play, Scored on Your Board

    Somebody mid-game with seven tiles in front of them and a specific gap on the board, who wants the highest-scoring word that fits it — counting the premium squares under the play and the blank that scores nothing — not a list of every word their letters could theoretically spell.

  • Wordle Solver — Find Every Word Your Clues Still Allow

    Somebody three guesses in and stuck, looking at a row of green, yellow and grey tiles, who wants the list of words those tiles still allow — and ideally which of them to try next — without reading an explanation of the game they are already playing.

  • Unscramble Words — Word Unscrambler and Finder

    Somebody staring at a rack of letters — mid word game, mid crossword, or just handed a jumble — who wants every real word those letters can make, not a puzzle to solve about the tool itself.

Word tools

One family, because the audience is the same person

Someone stuck on seven tiles in a word game and someone checking whether "quixotry" is really a word are close enough to the same visit that they belong under one roof, the way the developer tools sit together because they are all "do one small thing to a string" even though a hash and a UUID have nothing else in common.

Close is not the same, though, and two of these three are close enough to be worth telling apart out loud. The unscrambler is for a rack and no board — a jumble, a crossword clue, letters before the game starts — and it answers "what can these letters spell". The Scrabble finder is for a specific gap on a specific board and answers "what should I play here", which is a different question because the answer depends on the premium squares and on a blank scoring nothing. If you have no board in front of you, the unscrambler is the one you want.

What unifies this family is the material, not the operation: letters and words, rather than PDFs or images. As more word tools land here, that is the test each one has to pass — does it work on the word itself, not on a file that happens to contain one.

Everything here runs on your own machine

A rack of letters for a word game is a small thing to worry about, and it is still not something this site sends anywhere. The dictionary these tools search is downloaded once, as plain text, and every search after that is arithmetic in the tab rather than a request — the network panel during a search is the way to check that rather than a claim to take on trust.

That also means there is no server cost per search, which is why nothing here is metered, queued or capped at some arbitrary count of lookups. A million searches cost the same to run as one, because they are not requests to begin with.

Words are not files, and that changes what a tool needs to know

A file-based converter cares about bytes: a container format, a codec, a compression scheme. A word tool cares about none of that — it needs a dictionary, an idea of what a "match" means for the specific question being asked, and nothing else. That is a much smaller problem than a converter, which is part of why a family built around it can hold several small tools without any one of them growing complicated.

The trade-off runs the other way too. A converter takes a file whose shape it already understands and produces another one; a word tool takes something as loose as "some letters" or "a string" and has to decide, on its own, what a useful answer even looks like. Unscrambling a rack answers "what can this build"; a future tool comparing two blocks of text would answer a completely different question using the same raw material — text — which is the actual thread connecting everything that will live under this hub.

Where this fits next to the rest of the site

The developer family answers "do this specific operation to a string a program produced" — decode this token, format this JSON. This family answers a plainer kind of question, the sort a person rather than a program asks: what words can I make, is this spelled the way I think it is, what changed between two drafts. Neither belongs inside the other, which is the same reasoning that kept the QR family separate from both.

It also sits differently in how it gets used. A developer tool is usually one stop in the middle of a task that continues somewhere else — a terminal, an editor, a deployment. A word tool is more often the whole task: someone arrives stuck on a rack of letters, gets an answer, and is done. That difference is part of why this hub is built to stay simple rather than to accumulate the kind of settings a developer tool collects over time.

Word tools: common questions

Is this family only for word games?

No — word games are the first and clearest use, but the tools work the same way whether the reason is a game, a crossword, a vocabulary check or simple curiosity about which words a set of letters can make.

Is anything I type sent to a server?

No. The dictionary is fetched once as a static file and every search runs in your browser against it, so nothing you type is uploaded — the network panel will show a search producing no request at all.

Will more word tools be added here?

That is the reason this is a family page rather than a single tool with its own hub. Anything that works on words rather than files belongs here as it is built.

Do I need an account?

No, and there is no limit tied to one. Every tool in this family runs locally, so there is nothing on our side to meter or gate behind a sign-up.

Other kinds of tool