About Editly
Editly is built and maintained by one person: a software developer working under the handle kodewright, with more than ten years of professional web development behind him. Not a startup, not a content farm, not a team of contractors — one engineer who got tired of the state of online text tools. Most word counters were slow to load, buried under ads, or vague about what happened to your text once you pasted it in. So he built the alternative: fast, distraction-free, and architecturally incapable of seeing what you write.
Who Builds Editly
kodewright is a senior web developer with over a decade of professional experience, specialising in front-end architecture and browser-side text processing. Editly is a solo project — every tool on this site, every line of its Nuxt 4 and TypeScript source, every readability formula and Unicode segmentation decision, was designed, written, tested and shipped by the same person. That matters for a tool you trust with your writing: there is no ambiguity about who handles your data, because the answer is nobody. The code runs on your machine and the person who wrote it never sees a byte of it.
Background
- 10+ years building production web applications, from small tools to large single-page applications.
- Front-end specialist: Nuxt, Vue and TypeScript, with a focus on performance budgets and rendering behaviour rather than framework fashion.
- Deep experience with Unicode text handling — the Intl.Segmenter work behind the word counter came from repeatedly hitting the limits of whitespace-splitting in real projects.
- Privacy-by-architecture advocate: every tool here is client-side by design, not by policy, because a promise you cannot technically break is worth more than one you can.
The Mission
The goal is simple: the most useful text analysis tool on the web, with no compromises on privacy. Every computation runs directly in your browser using JavaScript — word counts, readability scores, keyword density and speaking time are all calculated locally, on your device. Nothing you type is ever transmitted to a server. That was a deliberate architectural decision, taken before the first tool shipped. Client-side processing means your writing stays yours, whether you are working on a novel draft, a legal memo or a confidential business document. There is no access to your content, because the system was designed so that access is impossible.
Why Choose Editly?
Privacy First
Your text never leaves your device. All analysis runs in-browser via JavaScript — no server uploads, no logging, no risk of your writing being stored or shared with third parties.
Deep Text Insights
Beyond simple counting: Flesch-Kincaid Grade Level, Flesch Reading Ease, keyword density with stop-word filtering, estimated reading time, and speaking time — all updating in real time as you type.
Built for Performance
Built with Nuxt 4 and Vue 3 by a developer with ten years of production experience, the interface loads instantly and responds on every keystroke. No spinner, no delay — stats are always current without a page reload.
Distraction-Free Interface
A focused workspace with full dark mode support, a bilingual interface (English and Ukrainian), and a toolbar that keeps every text editing tool within reach without leaving the page.
Accuracy and Methodology
Algorithm accuracy is taken seriously here. Word counting uses the Intl.Segmenter API — the W3C Unicode text segmentation standard built into modern browsers — instead of naive whitespace splitting, so it produces consistent results across Latin, Cyrillic, CJK and other script systems, including languages like Chinese and Japanese that don't use spaces between words. Readability is measured using two established formulas: the Flesch-Kincaid Grade Level (a standard used by educators and the U.S. Department of Defense since the 1970s) and the Flesch Reading Ease score (widely used in publishing and plain-language writing standards). Keyword density analysis strips common stop words before counting, so the results reflect your actual vocabulary distribution rather than grammatical filler. Speaking time is estimated at 130 words per minute and reading time at 200 words per minute, based on published averages for adult native speakers.
How This Content Is Made
The written content on this site — the guides, the tool explanations, the FAQ answers — is produced with AI assistance, then edited, fact-checked and signed off by a human before it goes live. AI is a drafting tool here, not an author. Every number, formula and claim about how a tool behaves is verified against the actual implementation, because the person editing the copy is the person who wrote the code. Where a figure is quoted — 130 words per minute for speech, the Flesch-Kincaid coefficients, the way Intl.Segmenter treats hyphens and emoji — it has been checked against the running tool, not generated and hoped for. The tools themselves are hand-built and covered by an automated test suite.
Who Uses Editly?
- Students: checking essay length against strict academic word count limits before submission.
- Content creators: measuring keyword density and readability before publishing blog posts or web copy.
- Public speakers and coaches: pasting a speech script to estimate delivery time at a natural speaking pace.
- Professional writers and editors: monitoring reading level and document length across multiple drafts.
Get in Touch
Editly is built and maintained by kodewright. Every message that comes through the contact form is read by the person who wrote the code — not a support queue — and that feedback decides what gets built next. If you have found a bug, want to suggest a feature, or have a question about how any of the analysis works, get in touch. You can also follow the work on social media.
Email: [email protected]
Contact Us: Contact Us
