Skip to content
Draftwell

Draftwell

Small tools for drafts, lists, and payloads

Draftwell is a desk of ten utilities I kept rebuilding in scratch files: a word count that matches a plain-text brief, a readability check that refuses to score a headline, a JSON formatter that shows the parser error instead of “fixing” it, and a few others in the same vein. They run in the browser. The text you paste is not sent to a server for those tools.

The pages under each tool explain who it is for, the steps, what the numbers mean, and where they lie. If a limit matters (a syllabus, a print size, a password you might actually use), read that section before you trust the output. Guides sit beside the tools when the idea needs more than a widget.

What you can do here

Writers use the counter and the readability checker when an editor says “keep it under 800 words” or “this reads like a manual.” Hearing a paragraph aloud catches a repeated word that the eye skips. None of that replaces an editor. It shortens the boring part.

Developers use the JSON formatter when a webhook body is one long line, Base64 when a tutorial says “just btoa it” and then breaks on a name with an accent, and the UUID generator when a prototype needs an id before the database exists. The password generator is for throwaway accounts. It is not a vault.

The QR tool is the one people print. Error correction and size are on the page because a code that looks fine on a laptop fails in a dim hallway. The Wi‑Fi option escapes odd characters in the network name; you should still scan it with a phone before you tape it to a router.

Placeholder text is here because layouts need it, and because it should never ship. The guide on that page says the same thing in more words. If a page on this site is indexed, it is meant to be read by a person, not filled with Latin.

How the pages are organized

  1. The tool itself, at the top, so you can try it before reading.
  2. Who it is for, the steps, and how the calculation or encoding actually works.
  3. A worked example, the mistakes that show up in practice, and the limits.
  4. Questions people ask after the first wrong result, plus a link to a longer guide.

If something on a page is wrong, the contact address is saccessnow@gmail.com. Corrections are part of keeping the site useful. The editorial policy says how that works, and the about page says who is responsible for it.

Notes

Longer notes sit beside the tools: how a whitespace count disagrees with Word, why a readability score will punish the caveat, and what not to encode into a QR code. They were published together, not dripped out as a calendar.

All notes

Guides

The guides are the part you can read without opening a tool. They cover the disagreements between word processors, what a Flesch score is actually measuring, and why Base64 is not a lock.