The job
When to reach for the Claude email humanizer
You have drafted an email with a model, or written it yourself in the register everybody writes work email in, and it reads like a template. Paste the body here, press Rewrite, and it comes back plainer: opener gone, hedges thinned, sentence lengths varied.
It runs on our server, 5 runs per rolling 24 hours, up to 12,000 characters each, with an optional instruction of up to 300 characters. Five runs is a handful of emails a day, so it suits the message you actually care about rather than every reply in the queue.
The loop
How to humanize an email in three steps
The first step is the one that prevents the expensive mistake.
- Step 1
- Select the body of the email only. Leave out the subject line, your signature block, the legal footer and any quoted thread history.
- Step 2
- Say what you want in the instruction box: shorter, warmer, more direct, keep the ask in the first line. Then press Rewrite.
- Step 3
- Check names, dates, figures and links, then paste the result back between your subject line and your signature.
Before you paste
Four things to keep out of the email humanizer
This route rewrites everything it receives. There is no protected field, no fixed-text marker and no subject line input, so the defence is what you choose to paste.
- Your signature block
- Job title, phone number, company address. All of it is text and all of it can come back reworded.
- Links and tracking URLs
- A rewritten link is a broken link. Refine, a competing tool, treats links as fixed by design. This one does not, so keep them out.
- Quoted thread history
- Paste only what you are writing now. Otherwise someone else's words get rewritten and sent back to them in a new form.
- Legal or compliance wording
- If a disclaimer was approved in a specific form, a rewrite changes it. Refine raises the same point about its own tool and it applies here too.
Self-edit first
The shape of an AI email, and what to delete
Refine names the pattern precisely: "formal openers, three-sentence body, a vague closing", with "corporate hedges" and "three-sentence symmetry" through the middle. RewriteAI names the single most common opener, "I hope this email finds you well".
Deleting those yourself takes ten seconds and spends none of your five runs. It also tells you something useful: if the email collapses once the padding is gone, the problem was never the tone. That is the point to stop and rethink what you are asking for.
Manage expectations
What the rewrite will not fix about your email
Refine puts the honest version on its own product page: reply rate is driven by relevance, timing and the offer, not by tone alone. It describes humanizing as one of the cheaper wins available, which is a fair description of what any tool in this category is worth.
Before you spend a run, check the things that decide the outcome. One ask, not three. The ask in the first three lines. The right recipient. A reason to reply this week rather than eventually. If those are wrong, a warmer version of the same email lands in the same place.
Length
Long emails, threads and the character cap
12,000 characters per run is a lot for this category. Refine's free tool takes 200 words and RewriteAI's free tier takes 300 words per input with 500 words a month, so a long project update or a detailed reply fits here where it would not fit there.
Use the counter above the box both ways. It tells you whether your draft fits before you run, and it tells you whether the result came back longer than what you pasted. If it grew, cut the first and last paragraphs rather than running a second pass.
Where it stops
What this email humanizer does not do
No detector promise, no deliverability claim and no reply rate figure. One competing tool advertises 99% resistance to AI detection and three times the reply rate of a raw AI email. We have no visibility into any detector or mail filter and no measurement of our own, so we say nothing.
No writing from scratch, no personalisation from a contact record, no tone dropdown, no file upload, no API, no account and no saved history. What you get is one rewrite of one pasted body, five times a day.
There is no language claim either. Refine states that it is built for English and that output quality drops sharply for other languages, which is a useful thing to publish. We have measured nothing comparable, so rather than borrowing their boundary or implying we have none, we say that no language claim is established here.