The draft, image, or document should remain the centre of the interface.
01Small tools.
Serious intent.
InstantWordCount began with one useful question—how many words are here? It grew around the next questions people ask when a draft needs to become something finished.
Finish the work between draft and delivery.
Writing rarely ends when the word count is right. There are headings to check, paragraphs to tighten, metadata to prepare, images to resize, backgrounds to clean, and PDFs to assemble.
InstantWordCount connects those practical jobs without asking people to create another account, learn another complex platform, or send ordinary work through unnecessary systems.
The decisions behind the interface.
These principles matter more than adding another button.
Show useful information while it can still improve the result.
02Use browser-side processing when the task can be completed safely on-device.
03Prefer direct controls and clear defaults over settings that merely look advanced.
04Use real progress, clear limitations, and warnings that appear only when relevant.
05Every workflow should lead to a reliable result people can download and use.
06Built outward from a real workflow.
The toolkit did not begin as a list of unrelated utilities. Each layer came from the next practical step in producing useful content.
See how the workflows connect →- 01MEASUREWord counting
Fast counts, reading time, speaking time, and basic text signals.
- 02IMPROVEWriting workspace
Drafting, readability, revision support, local projects, and exports.
- 03PACKAGESEO and publishing
Headlines, metadata, social previews, and structured publishing helpers.
- 04FINISHImage and PDF studios
Visual preparation, document assembly, conversion, and reliable downloads.
Useful whether you publish every day or once a semester.
Draft, review, measure, and prepare copy without losing the thread.
Check assignments, reading time, structure, and everyday document work.
Prepare SEO copy, social previews, images, and documents for release.
Handle recurring production tasks without another expensive platform.
Local when possible.
Clear when it is not.
Normal text analysis and many supported image and PDF operations are designed to run in your browser. Preferences and local history use browser storage.
Some specialist features may load models, libraries, or external resources. Those workflows should identify their requirements where relevant rather than making a blanket privacy promise.
Read the privacy policy →Less tab chaos.
More finished work.
Start with the draft, file, or task already in front of you.