FAQ

Yes—within ~1% on standard prose. Hyphenated words count as one, and numbers alone count as words, matching the typical behavior users expect from document editors.

Sentences end on . ! ? (and ellipsis). Paragraphs are separated by a blank line—pressing Enter once won’t split paragraphs; you need an empty line between them.

Reading time uses an estimate based on ~200–250 words per minute, and speaking time uses ~130–150 words per minute. They’re meant as practical approximations of average adult pace.

No. Everything runs in your browser; no text is uploaded or logged.

camelCase starts lowercase (userName), while PascalCase capitalizes every word including the first (UserName). PascalCase is commonly used for classes, camelCase for variables/functions.

snake_case is common in Python/Ruby and in database column names. kebab-case is used in URLs and CSS class naming because hyphens are more URL/markup friendly than underscores in many contexts.

Yes—acronym runs are kept together and then split before the next capitalized word, so inputs like XMLHttpRequest preserve the expected word boundaries.

It collapses extra spaces between words, trims leading/trailing whitespace, and reduces runs of multiple blank lines down to normal paragraph spacing (keeping a clean, predictable structure).

No. It collapses excessive blank lines but preserves single line breaks and standard paragraph structure. If you have a proper paragraph (two newlines), it stays intact.

Copying from PDFs/Word often introduces irregular spacing, trailing spaces, and broken formatting. This tool normalizes that clutter so the text behaves consistently when you paste it elsewhere.

Yes. It compares lines as-is, so identical text in different cases is treated as different lines.

Only exact duplicate lines are removed. If you want blank lines removed as well, run Whitespace Cleaner first to normalize spacing.

Cleaning email lists, deduplicating copy-pasted data, removing repeated log entries, and tidying configuration output where the same line can appear many times.

It uses the browser’s built-in random number functions. Each line has an equal chance to be picked.

Only if “Allow duplicates” is checked. Otherwise, picks are unique for that run.

With duplicates off, you can’t pick more unique lines than exist—so the tool effectively caps at the total non-empty line count.

Spaces become hyphens. Accented characters are converted to their plain equivalent (é → e). Punctuation and special characters are stripped.

Google treats hyphens as word separators, while underscores can be read as word-joining. Hyphens are generally the SEO-friendly choice for URL slugs.

Yes. Slugs are lowercased to avoid case-sensitive URL issues and reduce duplicate-content variants.

Yes. Toggle “Use regex” to enable full pattern matching, including capture groups.

Toggle “Replace all” versus “First only” depending on what you’re correcting.

Yes. Toggle case-sensitivity off if you want “Cat” and “cat” treated the same.

Nothing directly. It’s a scrambled fragment of a classical Latin text by Cicero (45 BC), altered centuries ago so it’s intentionally nonsensical.

It mimics real letter and word-length distribution, so it looks visually realistic without distracting readers with readable, meaningful copy.

No. Search engines and users often flag it as low-value content—replace it before publishing.

It uses a Longest Common Subsequence (LCS) approach to identify shared portions, then highlights what’s added, removed, or changed.

Yes. Toggle Ignore Case, Ignore Whitespace, or Ignore Empty Lines to focus on meaningful content changes.

git diff compares versioned files inside a repository. This tool compares any two text blocks with no setup required.

Word frequency ranks every word by how often it appears. Keyword density focuses on how often one specific target term appears as a percentage of total words.

Generally 1–2% for a primary term. Much higher can look like keyword stuffing to search engines.

Yes. By default, common words often dominate the list too—use frequency to inform editing decisions, not just to chase “perfect” percentages.