If your English copy sounds translated even though your grammar is clean, you’re not imagining it. You wrote the draft. You ran it through Grammarly. No red lines. You sent it off.
A native editor came back with a rewrite and the note: “Great content—just made it flow better.” You read the two versions side by side. You can’t name a single grammar rule that was broken in yours. But theirs sounds right, and yours sounds like a translation.
That gap is what I want to talk about. It has a name, a cause, and a fix. It is not your grammar. It is not your vocabulary. And it is not something you solve by “reading more native writers,” which is the advice every non-native professional gets and nobody can operationalise.
Short answer up top: Copy that’s grammatically correct but reads translated is usually failing at register — the unwritten rules about how formal, how direct, and how rhythmically varied your sentences are for a given context. Grammar tools don’t check register. AI tools average it out. Native readers feel it in under two seconds.
The rest of this post is the diagnosis, a framework you can use on your own drafts, and the before/afters that make the gap visible.
The scale of the problem (and why it’s your problem now)
About 373 million of the world’s 1.5 billion English speakers are native speakers. The remaining 1.1 billion — roughly three out of four — use it as a second language (The Language Doctors). That means most professional English writing today is produced by people in your position, not in mine-is-perfect position.
The ceiling you’re hitting isn’t rare. It’s the default.
What changed recently is the exposure. The EF English Proficiency Index 2024, based on test results of 2.1 million non-native English speakers across 116 countries, reports an ongoing softening of worldwide English proficiency (PR Newswire), while ChatGPT, Claude, and Gemini now produce copy that reads more native than most non-native drafts—in seconds, for free. That’s the squeeze: your ceiling is visible in a way it wasn’t two years ago, because the comparison is immediate and one click away.
I’m going to call the thing you’re bumping into The Register Gap. It’s the most useful label I’ve found for it, and I’ll come back to it a few times.
The Register Gap: what’s actually breaking in your copy
Grammar is a rulebook. Register is a social contract. Grammar asks, “is this sentence legal?” Register asks “does this sentence belong in this room?”
When a native reader says your copy “sounds off,” they are almost never talking about a grammar violation. They are telling you the sentence is legal but standing in the wrong room. Too formal for a SaaS landing page. Too direct for a customer apology. Too literal for a joke. Too long for a hook.
The reason this is so hard to fix alone: your English teachers taught you grammar. Nobody explicitly taught you register. You picked it up—if you picked it up—from books, films, and reading native writing for years. If your input was mostly academic English, your output will always skew academic. If your input was British, your output will always have a British tilt, which will feel slightly off on an American product page.
AI doesn’t help as much as you’d think. When you ask ChatGPT to “fix” your copy, it usually flattens your register toward a middle-of-the-road American business voice. Safer, but also more generic. You’ve traded “sounds translated” for “sounds like everyone else’s LinkedIn post.”
The three registers where non-native writers lose the reader
From the drafts I see most often when reviewing copy from non-native teams, The Register Gap shows up in three predictable places. Not grammar. Register.
1. Over-formal where the context asks for casual
❌ In the event that you encounter any issues, please do not hesitate to reach out.
✅ If anything breaks, email us.
❌ We are pleased to announce the availability of our latest product update.
✅ New update’s out. Here’s what’s in it.
The first versions are legal English. They are also standing in the wrong room. A product email in 2026 is a coffee-shop conversation, not a board meeting.
2. Translated idioms that almost work
❌ This feature will solve a big headache for your team.
✅ This feature takes one annoying job off your team’s plate.
❌ Let me share some words about our mission.
✅ Quick note on what we’re trying to do.
“Solve a headache” is a reasonable literal translation from several languages. Native English says “take something off your plate,” “save you the trouble,” or “stop you from pulling your hair out.” The meaning transfers. The idiom doesn’t.
3. Rhythm that never changes
❌ Our platform helps teams work better. Our platform saves time. Our platform makes collaboration easier.
✅ Our platform helps teams work better. It saves time. Collaboration just stops being the hard part.
The grammar in the first version is immaculate. The problem is that every sentence has the same length, the same subject, and the same structure. Native English prose varies in rhythm instinctively. Non-native prose often doesn’t, because the rhythm was never taught as a separate skill from grammar.
This is the rhythm problem I wrote about in more detail in why your English writing sounds unnatural — if you want the deeper version.
How to see The Register Gap in your own draft
Three tests, in order. You can run all three in under ten minutes on any piece of copy.
Test 1: The room test. Read the sentence out loud. Now ask: would a real person, in the real context this copy will be read in, actually say this? A login page confirmation that says “We are pleased to confirm your successful authentication” has failed the room test. A friend texting “please be advised” has failed the room test. If the answer is “a human wouldn’t say this here,” your register is off, not your grammar.
Test 2: The translation sniff test. Take any sentence that feels slightly off to you. Translate it back into your first language, in your head. If the translation is suspiciously clean and the English feels slightly weird, you probably wrote the first-language sentence first and translated it. I covered the deeper version of this in stop thinking in English while you write. The fix isn’t to translate better — it’s to stop translating and draft in the register you want, even if it comes out clumsier at first.
Test 3: The rhythm test. Count the words in each of your last five sentences. If four of them are within two words of each other, your rhythm has flatlined. Cut one sentence in half. Merge two others. Vary the lengths until your eye stops noticing a pattern.
If you want a shortcut while you’re building the habit, the Natural English Edit is the 15-pattern checklist I use on my own drafts—each one paired with the ChatGPT prompt that fixes it. It’s the register-gap problems in a form you can run on one page in under ten minutes.
What I’m not going to tell you
I’m not going to tell you to “erase your accent” in writing. A non-native voice is not a defect to scrub. Plenty of the most memorable English copy in the last ten years was written by non-natives with an audible register—think of the directness in a lot of Scandinavian or German-founded tech copy, or the slight formality that works beautifully in high-end Japanese brand English.
What you want is register control, not register erasure. The goal is to know which room the sentence is standing in and to put it in the right room on purpose. Sometimes “pleased to announce” is exactly right. Sometimes “a new update’s out” is. The skill is knowing which.
That’s a different framing than most advice for non-native writers offers, and it’s the one I’m going to keep coming back to on this blog.
Where to go next
If you want to keep working on this:
- Read why your English writing sounds unnatural for the rhythm-and-flow side of the problem in more depth.
- Read the difference between correct English and natural English for the framing that sits underneath The Register Gap.
- Or start with the Natural English Edit — the 15-pattern checklist for readers who prefer a tool over another blog post.
FAQ
Why does my English sound translated even when the grammar is correct? Because grammar and register are different skills. Grammar asks if a sentence is legal; register asks if it fits the social context. Most translated-sounding copy fails on register — too formal, wrong idiom, flat rhythm — not on grammar.
Can Grammarly or ChatGPT fix copy that sounds translated? Partially. Grammarly catches almost no register issues because it’s built on grammar rules. ChatGPT can smooth the register, but it usually flattens your voice into generic American business English at the same time. Both are useful; neither is a complete fix.
Is “sounds translated” the same as “bad English”? No. Copy can be grammatically excellent and still sound translated, and it can be technically imperfect and still sound native. They’re separate axes. Register is about social fit, not correctness.
How long does it take to close The Register Gap? Months of targeted practice, not years of general reading. The fastest progress comes from editing your own drafts against a specific checklist, not from passive reading. Three to six months of deliberate self-editing moves most professional writers visibly closer.
Should non-native writers try to sound native? Aim for register control, not register erasure. Your first-language instincts can sharpen your English if you use them deliberately — directness, clarity, unusual metaphors. The goal is picking the register on purpose, not hiding your background.
Does AI make the translated-sounding problem worse or better? Both. AI now produces smoother-register English than most non-native drafts, which exposes the gap. It also gives you a free rewriting tool that can teach you register faster than any book. Whether it helps depends on whether you use it to learn patterns or to outsource thinking.