Text Content Tools
Free text and content tools to clean up, analyse and reshape your writing. Count words and characters, remove duplicate lines from a list, check text for plagiarism and generate an alternate draft with the article rewriter.
What "Text Content Tools" Covers
This category groups the five tools on this site that work directly on a block of text you paste in, rather than on a URL, a domain, or a whole website. Between them they cover four different jobs: counting (words, characters, lines), cleaning (stripping repeated lines out of a list), checking (whether a passage already appears somewhere else online), and rewriting (swapping words for synonyms to produce an alternate version of a passage). None of these tools crawl a site, look up a domain, or touch anything outside the text box you paste your content into.
That narrow scope is deliberate rather than a limitation worth apologizing for. A word counter that also tried to check backlinks would be worse at both jobs. Each tool here does one specific text-processing task, does it in a way you can actually verify (the mechanics section for each tool below is sourced from reading the tool's own code, not from marketing copy), and gets out of your way once it's done.
Why Text-Content Hygiene Matters for SEO and Content Work
Three separate problems show up often enough in day-to-day content work that having a dedicated free tool for each one is worth more than it sounds. None of these are exotic; they're the kind of small, boring issues that quietly cost rankings or waste time when nobody catches them before publishing.
- Duplicate content risk. Publishing a passage that's already indexed elsewhere, word-for-word, doesn't automatically get a page penalized, but it does put it in direct competition with the original source for the same search real estate, and search engines generally favor whichever version they found first. Checking a draft against the live web before it goes out catches this while it's still cheap to fix, not after the page is published and already competing against its own source.
- List hygiene for exports and merges. Any list built by combining more than one source (keyword exports from two research tools, a URL list assembled from a CMS export plus a manual add-on list, an email list built up from several signup sources over time) tends to pick up exact repeats. A merged list padded with duplicate entries makes counts look inflated and wastes processing time on anything downstream that has to touch every line once.
- Readability and format discipline. A word count against a platform's stated limit, a character count against a meta description's practical display width, a line count against a form field's row limit: these are unglamorous checks, but getting them wrong after the fact (a meta description that gets truncated in search results, a bio field that overflows its container) is a worse outcome than a ten-second check beforehand.
None of the five tools below solves all three problems on its own. Combined, in the order covered in the workflows section further down this page, they cover most of what a person publishing text online actually needs to check before hitting publish.
The 5 Tools in This Category
Each of the following runs on this site right now. The "how it actually works" line for each one is based on reading the tool's own client-side JavaScript or server-side PHP, not on assumption, so a claim here that sounds unusually specific (an exact function name, an exact mechanic) is specific on purpose.
Word & Character Counter
The simplest tool in this category, and the one most people reach for first. Paste text in, click count, get a word total and a character total back. How it actually works: this runs entirely in your browser. There's no upload, no server round-trip; a plain JavaScript function splits your pasted text on whitespace to get the word count and reads the raw string length for the character count. That means the count appears instantly, and your text never leaves the tab you're sitting in.
Reach for this when you need a fast, no-friction sanity check against a stated limit: a platform's word cap on a bio or listing, a rough sense of an article's length before you paste it into a CMS, or a quick character count for something with a hard cap you don't want to exceed. It's not a fit if you need a live, real-time count while you're still typing (see Line Counter below, which does that) or if you need anything beyond a raw word/character total, like a readability score; this tool doesn't calculate one.
Line Counter
Where the Word & Character Counter is a click-and-check tool, this one counts live, as you type. How it actually works: a jQuery plugin (`textareaCounter`, running client-side, same no-upload behavior as the counter above) listens for keystrokes in the text box and updates the character and line counts on every input event, splitting on line breaks for the line total. Because it's watching the field continuously rather than waiting for a button click, it's built to sit underneath a field that has a real constraint you're writing against, not just to run once on a finished block of text.
Reach for this when you're actively drafting something with a line or character constraint you want to watch while writing, rather than checking after the fact: a list you're building line-by-line where you want to keep track of the running count, or any text box where seeing the number update as you type beats stopping to run a separate check. It's not a fit for a quick one-off count on text you've already finished writing and just want a final total for; the plain Word & Character Counter is faster for that, since you don't need to paste into a field and watch it update.
Duplicate Line Remover
Takes a list, one item per line, and strips out any line that's an exact repeat of a line already seen earlier in the same list, keeping the first occurrence and preserving the original order. How it actually works, verified directly against this tool's own JavaScript: it runs entirely client-side (no upload, same as the two tools above), splits the input on line breaks, walks the list top to bottom, and compares each new line against everything already kept using a plain case-sensitive string match, with no whitespace trimming and no sorting.
Two lines differing only by capitalization, like Example.com and example.com, are treated as different and both survive; the same is true of a line with a stray trailing space against its otherwise-identical twin without one.
Reach for this before submitting, emailing, or uploading any list assembled from more than one source: a merged keyword export, a URL list combined from a CMS export and a manual addition, an email list built from multiple signup points over time. It's not a fit if you need near-duplicate detection rather than exact-match: it won't catch a URL that differs only by a trailing slash or an http-vs-https protocol, or two keyword phrases that mean the same thing but are worded differently. Standardize casing and whitespace in your list yourself first if those differences matter to your specific list.
Free Plagiarism Checker
Checks whether a passage of text already appears somewhere on the public web. How it actually works, verified against the tool's own JavaScript and PHP: it splits your pasted text into roughly 40-60 character phrase segments, then submits each segment, one at a time, to a backend that queries the Google Custom Search JSON API, wrapping the phrase in quotation marks to force an exact-match search. If Google's index returns a result for that exact phrase, the segment is flagged as already published somewhere; if Google returns nothing for it, the segment is flagged unique.
That's worth stating plainly because it means this tool checks against the live public web through Google's own index, not against a private, proprietary database the way some paid plagiarism tools are marketed. It's the same general approach most free plagiarism checkers use, just framed here honestly instead of as some kind of proprietary detection engine.
Reach for this before publishing anything you want to be sure reads as original, especially content that's been spun, translated, or lightly reworded from an existing source (see the workflow section below for pairing this with the Article Rewriter). It's not a fit for catching paraphrased content that's been reworded enough to change the exact wording while keeping the same meaning; an exact-phrase search engine check can't flag that kind of similarity; it only catches passages that are still an exact or near-exact wording match to something already indexed.
Article Rewriter
Takes a block of text and produces an alternate version by swapping recognized words for synonyms. This is the one tool in this category worth an extra sentence of honesty about how it works, because the name invites an assumption the tool doesn't actually deliver on. How it actually works, verified against the tool's own PHP: it's not an AI paraphraser. It reads a local, pipe-delimited synonym database file and, for each word in your text that has an entry in that file, randomly substitutes one of the listed synonyms.
That's the classic word-swap "article spinner" mechanic, not a modern language-model rewrite, and it produces exactly the kind of output that mechanic implies: some substitutions read naturally, others land awkwardly or change a word's sense slightly, and the result generally needs a manual read-through and edit before it's fit to publish anywhere.
Reach for this as a starting point for producing an alternate draft of a passage you plan to edit by hand afterward, not as a finished-output tool. It's not a fit for anything you plan to publish unedited: a word-swap spinner's output is a known, recognizable pattern to both human readers and to search engines that have seen this exact mechanic for well over a decade, and publishing spun text without a real edit pass is more likely to read as low-quality than to pass as original writing. Pair it with a genuine editing pass, and check the result with the Free Plagiarism Checker above before publishing; see the workflow section directly below for how those two fit together.
What This Category Doesn't Cover
Worth being clear about the boundary, since it's easy to assume a text-tools category covers more than these five specific jobs. None of the tools here check grammar or spelling; there's no proofreading pass built into any of them. None of them calculate a readability score (Flesch-Kincaid or similar), suggest better word choices for tone, or flag passive voice. None of them optimize a passage for a target keyword the way an on-page SEO content tool would; that job, along with keyword density checking, lives in the separate Keywords Tools category on this site, not here.
The line between this category and Meta Tags Tools is also worth a sentence. Word & Character Counter and Line Counter here measure any block of text you paste in, generally. If you're specifically working on a page's meta title or description tags, the Meta Tag Generator and Meta Tags Analyzer live in their own Meta Tags Tools category on this site, separate from the general-purpose text tools covered here.
Comparison at a Glance
All five tools are free, work directly in the page with no signup, and need nothing installed. Where they differ is what they check, whether the check happens entirely on your own machine or involves an outside service, and what job each one is actually built for.
| Tool | Primary job | Runs | Best for |
|---|---|---|---|
| Word & Character Counter | One-off word/character total | Client-side only, no server call | A fast final count on finished text |
| Line Counter | Live character/line count while typing | Client-side only, no server call | Drafting against a running limit |
| Duplicate Line Remover | Strip exact-repeat lines from a list | Client-side only, no server call | Cleaning a merged export before use |
| Free Plagiarism Checker | Check if a passage already appears online | Server-side, queries the Google Custom Search API per phrase | A pre-publish originality check |
| Article Rewriter | Produce a synonym-swapped alternate draft | Server-side, local synonym database lookup | A rough starting draft you'll edit by hand |
The client-side-vs-server-side distinction in that table is more than a technical footnote. The three tools that run entirely in your browser never send your text anywhere, which matters if you're working with anything you'd rather not transmit: an unpublished draft, an internal list, a client's unreleased copy. The two server-side tools need to send data out by design, because checking against Google's index or looking up a synonym database is, by definition, not something a browser tab can do entirely on its own.
Common Mistakes That Waste These Tools' Value
Each of these five tools does exactly what it's built to do, but a handful of habits routinely undo that value before it ever helps anyone. None of these are exotic mistakes; they're the ordinary ways a genuinely useful free tool gets used badly.
- Treating every flagged phrase in the plagiarism checker as a real problem without reading what actually matched. A flagged segment sometimes turns out to be your own previously published work, a common phrase or a standard legal/technical term that legitimately appears on many pages, or a short fragment that's coincidentally identical without meaning anything. Open the matched result and look at it rather than reacting to the raw flagged count alone.
- Judging Article Rewriter output by how much it changed rather than how well it reads. A heavily-swapped passage isn't automatically a better starting draft than a lightly-swapped one; the synonym database doesn't know which substitutions land naturally and which don't, so the amount of change tells you nothing about the quality of what came out. Judge it by reading it, not by how different it looks from the original.
- Deduplicating a list after uploading it instead of before. If a tool downstream (an emailing platform, a bulk-submission form, a crawler) is going to process your list line by line, running the Duplicate Line Remover before that step, not after, is what actually saves the wasted work. Cleaning a list after it's already been processed doesn't recover the time or the API calls already spent on the repeats.
- Assuming a case-sensitive tool will catch case-different duplicates. The Duplicate Line Remover is exact-match and case-sensitive by design, covered in detail in its own section above. If your list mixes capitalization conventions from different sources, standardize the casing yourself before pasting it in; the tool won't infer that
Example.comandexample.comare meant to be the same line. - Treating a live character count as a substitute for checking the actual display limit. The Line Counter and Word & Character Counter both report raw counts against whatever number you're comparing them to manually. Neither one knows Google's practical meta-description display width or a specific platform's true character cap; you still need to know the real limit you're checking against, since the tools count accurately but don't know the target number on their own.
Practical Workflows: Combining These Tools
None of these five tools is meant to be the only step before publishing something. Used together, in a sensible order, they cover a lot more ground than any one of them does alone. Three sequences come up often enough to be worth laying out explicitly.
Producing and checking a reworded draft. Start with the Article Rewriter to get a synonym-swapped alternate version of a passage. Read through it and edit the awkward substitutions by hand; this step isn't optional, since raw spinner output reads exactly like what it is if it's left unedited. Once you've edited it into something you'd actually put your name on, run it through the Free Plagiarism Checker before publishing, to confirm the phrases that matter most don't still turn up an exact match somewhere else online.
Skipping straight from the rewriter to publishing, without the edit pass and the check, is the single most common way this category of tool gets misused.
Cleaning a merged list before it goes anywhere else. If you've combined a keyword export, a URL list, or an email list from more than one source, run it through the Duplicate Line Remover first, before uploading, emailing, or submitting it anywhere. This is worth doing even if you're about to feed the list into another tool that does its own deduplication internally: getting your real, unique count up front means you know what you're actually working with before the next step.
Once the list is clean, a quick pass through the Line Counter (or Word & Character Counter, for a one-off check) confirms your before-and-after totals match up the way you'd expect: original count minus the number of duplicates removed should equal the cleaned list's line count.
Drafting against a hard character limit. If you're writing something with a fixed character budget, a meta description, a social bio, a form field with a display cap, draft directly in a text editor while watching the Line Counter's live character total rather than writing blind and checking afterward. Once you've got a version that fits, a final pass through the Word & Character Counter isn't redundant; it's a second, independent confirmation of the same number using a different, simpler code path, which is a cheap way to catch a copy-paste mistake (an extra trailing paragraph you meant to delete, for instance) before you commit to publishing that exact text.
Which Tool Do You Actually Need
If you're not sure where to start, the scenario that brought you here usually points at one specific tool more than the others.
- "I just need a quick word or character count on something I've already finished writing." Word & Character Counter. One paste, one click, done.
- "I'm actively writing something against a limit and want to watch the count as I go." Line Counter. It updates live while you type, so you're never guessing how much room you have left.
- "I've merged a list from two or more sources and it's probably got repeats in it." Duplicate Line Remover, before you do anything else with that list.
- "I want to know if this text already exists somewhere else online before I publish it." Free Plagiarism Checker, on the version you're actually about to publish.
- "I need a rough alternate version of a passage to start editing from." Article Rewriter, treated as a starting point rather than a finished draft (see its section above for why).
- "I need more than one of these." That's normal. The workflows section above lays out the three sequences that come up most often in practice.
Frequently Asked Questions
Are all five of these tools actually free to use?
Yes. None of the five tools in this category requires an account, a signup, or a payment to use. They're free the same way the rest of the tools on this site are: available directly on the page, no gate in front of them.
Do any of these tools store or save the text I paste in?
It depends on the tool. Word & Character Counter, Line Counter, and Duplicate Line Remover run entirely in your browser and never send your text anywhere; nothing is uploaded or stored. Free Plagiarism Checker and Article Rewriter both involve a server call by design (one queries a search index, the other looks up a synonym database), so text you submit to those two does leave your browser as part of how the check or the rewrite gets done. See each tool's own section above for exactly how its server-side step works.
Which of these tools should I run first before publishing something?
It depends on what you're publishing and where it came from. If you started from an existing draft and just need a final check, run the Free Plagiarism Checker last, right before publishing. If you built the draft with the Article Rewriter, edit it by hand first, then check it with the plagiarism checker; don't publish spun text straight off the rewriter without an edit pass in between. See the workflows section above for the full sequences.
How accurate is the Free Plagiarism Checker, exactly?
It's only as accurate as an exact-phrase search against Google's index can be. It's genuinely useful for catching passages that are still close to their original wording, since that's exactly what an exact-match phrase search is built to find. It won't catch content that's been reworded enough to change the exact phrasing while keeping the same meaning; that kind of paraphrase-level similarity is outside what a phrase-match search engine query can detect. Treat a clean result as "no exact-match copies found in Google's index," not as a guarantee of total originality.
Is the Article Rewriter's output safe to publish as-is for SEO?
No, and this site isn't going to pretend otherwise. The tool works by swapping words for synonyms from a fixed database, not by generating genuinely new writing, and unedited spinner output is a recognizable pattern, both to a human reader and to search engines that have been dealing with this exact category of tool for well over a decade. Use it as a starting point for a draft you'll edit by hand, not as a finished piece of content.
Do these tools have a limit on how much text I can paste in?
It varies by tool; check each tool's own page for specifics, since the limits (or lack of them) aren't identical across all five. The Duplicate Line Remover, for example, has no enforced line-count or character cap built in, though very large lists take longer to process than small ones because of how the comparison work scales with list size.
Will using these tools directly improve my search rankings?
Not on their own, and this site isn't going to claim otherwise. None of these five tools is a ranking factor by itself; there's no signal Google reads from the fact that you ran a passage through a word counter or a plagiarism checker. What they do is help you catch problems (duplicate content risk, an oversized meta description, a messy exported list) before those problems become live issues on a published page, where they can indirectly hurt how that page performs. Think of them as pre-publish quality checks, not as ranking levers in themselves.