Paraphrasing tools get compared by word limits and price. That's useful, but it skips the question that matters more: what did the rewrite do to my meaning?
Different tools rewrite text in fundamentally different ways, and each way breaks in its own way. Below I go through four approaches, what each one is good for, what free tiers currently allow (read from the vendors' own pages), and a small Python script that flags the most common damage: dropped numbers, lost names and flipped negations.
Four ways text gets rewritten
| Approach | How it works | Good at | Typical failure |
|---|---|---|---|
| Synonym swap | Replace words using a thesaurus or rules | Fast, predictable, keeps structure | Wrong sense of a word ("bank" the river vs the institution), awkward phrasing |
| Back-translation | Translate to another language and back | Produces genuinely different phrasing without a language model rewriting your content | Can drift on idioms, jargon and tone |
| LLM rewrite | A language model rewrites to a requested style (formal, shorter, simpler) | Fluent output, controllable tone and length | Can silently change facts, drop qualifiers or invent detail |
| Manual | You rewrite it | Full control | Slow |
None of these is "the best". They suit different jobs: tightening an email (LLM or manual), simplifying a dense paragraph (LLM), getting a second phrasing of a short sentence (back-translation or synonym swap), preserving exact technical wording (usually manual, or don't paraphrase at all).
Here are illustrative failures I wrote to show the kinds of damage to look for (they're examples, not outputs from any specific product):
| Original | Rewrite | What changed |
|---|---|---|
| "The API is not free; it costs $20 per month for 5 users." | "The API costs $20 monthly for 5 users." | The negation vanished |
| "In March 2024, Dr. Alvarez found the drug did not reduce symptoms in 62% of patients." | "Dr. Alvarez found in early 2024 that the medication reduced symptoms in most patients." | The meaning inverted and the number was lost |
| "The meeting moves to 14:30 on Friday." | "The session is now at 15:30 on Friday." | A number was quietly altered |
Fluent output hides these errors, because the rewritten sentence reads smoothly. That's why a mechanical check is worth having.
A short "did the meaning survive?" checker
It compares three things between your original and the rewrite: numbers, names (capitalised words in the middle of a sentence) and negations. It won't understand meaning. It only catches the cheap, high-impact mistakes.
import re
NEGATIONS = {"not", "no", "never", "none", "cannot", "can't", "won't", "isn't", "aren't",
"doesn't", "don't", "didn't", "without", "neither", "nor"}
def tokens(text):
text = re.sub(r"['’]s\b", "", text.lower()) # France's -> france
return set(re.findall(r"[a-z']+", text))
def numbers(text):
return {n.rstrip(".,:;-") for n in re.findall(r"\d[\d,.:%/-]*", text)}
def mid_sentence_caps(text):
out = set()
for sent in re.split(r"(?<=[.!?])\s+", text):
words = re.findall(r"[A-Za-z][A-Za-z'’-]*", sent)
out |= {w for w in words[1:] if w[0].isupper()}
return out
def check(original, rewrite):
report = {}
lost, new = numbers(original) - numbers(rewrite), numbers(rewrite) - numbers(original)
if lost or new:
report["numbers"] = {"lost": sorted(lost), "added": sorted(new)}
rt = tokens(rewrite)
names = sorted(w for w in mid_sentence_caps(original) if w.lower() not in rt)
if names:
report["names"] = {"lost": names}
ot = tokens(original)
lost_n, new_n = sorted((ot & NEGATIONS) - (rt & NEGATIONS)), sorted((rt & NEGATIONS) - (ot & NEGATIONS))
if lost_n or new_n:
report["negations"] = {"lost": lost_n, "added": new_n}
return report
Running it on the examples above:
>>> check("The API is not free; it costs $20 per month for 5 users.",
... "The API costs $20 monthly for 5 users.")
{'negations': {'lost': ['not'], 'added': []}}
>>> check("In March 2024, Dr. Alvarez found that the drug did not reduce symptoms in 62% of 1,200 patients.",
... "Dr. Alvarez found in early 2024 that the medication reduced symptoms in most of 1,200 patients.")
{'numbers': {'lost': ['62%'], 'added': []},
'names': {'lost': ['March']},
'negations': {'lost': ['not'], 'added': []}}
>>> check("The meeting moves to 14:30 on Friday, and Maria will attend.",
... "The session is now at 15:30 on Friday; Maria will be there.")
{'numbers': {'lost': ['14:30'], 'added': ['15:30']}}
>>> check("Paris is the capital of France.", "France's capital city is Paris.")
{}
The last case is the check working as intended: a valid rewrite produces an empty report. Limits: it's English-only, it can't see a changed verb ("increase" → "decrease"), and it will flag harmless changes such as "March 2024" → "early 2024". Treat it as a smoke alarm, not a judge.
What free tiers allow (read from the vendors' pages, Nov 2026)
Limits change often, so check the page before relying on any of this.
| Tool | Free input limit | Free modes | Other stated details | Source |
|---|---|---|---|---|
| QuillBot | "up to 125 words at a time" | Standard and Fluency; eight other modes are marked Premium | Page says no daily limit on free paraphrases | quillbot.com |
| Paraphraser.io | The page gives two different figures: "600 words limit free of cost" in the price section, and a "0 / 400" counter in the tool | Word changer, fluency, standard, formal and smooth, per the price section | "Unlimited text without any daily limit"; 20+ languages; the page has no statement on how your text is stored | paraphraser.io |
Two observations, both from reading those pages:
- A per-input cap and "no daily limit" can both be true: you can run unlimited chunks of 125 words. For a long article, that means splitting and re-checking transitions between chunks, which is exactly where meaning and tone drift.
- Where a page doesn't state data handling, I haven't assumed anything. If you're pasting confidential text into any online tool, read its privacy policy, or use the DevTools Network tab to see whether your text leaves the page.
I run a free paraphraser at ToolTiny, so I'm not going to rank it against these. Read its limits on the page itself like you would for any other.
When paraphrasing is the wrong tool
- Academic work: rewriting a source doesn't remove the need to cite it. The University of Virginia's honor committee puts it plainly: "paraphrasing without citing the original source is considered plagiarism" (source).
- Detection is moving too. In September 2025 Turnitin announced "AI bypasser detection," aimed at text that tools have modified to hide AI use. Coverage at the time noted it was limited to English and gave no accuracy figures (THE Journal). I'm not suggesting any tool should be used to evade that. The point is that a rewrite is not a substitute for your own understanding of the source.
- Legal, medical and technical text: precise wording often is the content. Rephrase the explanation around it, and quote the exact sentence.
A simple workflow that holds up
- Paste short chunks (a paragraph at most), not whole documents.
- Pick the approach that matches the job (table above).
- Run
check(original, rewrite), then read the rewrite aloud once. - Reread numbers, names and negations by hand. The script is a filter, not a proof.
- Cite the source if the ideas aren't yours.
Limits of this post
- The failure examples are illustrative and I wrote them myself; I did not benchmark any named tool's rewrite quality.
- The checker looks at three surface features of English text. It will miss subtle meaning changes and produce some false alarms.
- Tool limits are as stated on the vendor pages on the date I read them, and they change.
If you have a rewrite that fooled the checker, paste it in the comments and I'll see whether the script can be improved.
Top comments (0)