Why fooling them is so easy
A detector flags text that is smooth and even, because that is what AI writing looks like. So to fool it, you do not need a clever tool. You just need to make the writing less smooth. Any human editing does that on its own.
This is the catch built into the whole approach. The thing that makes text look human, a bit of mess and variety, is exactly the thing a light edit adds.
The common ways it happens
Light editing
Swap a few words, split a long sentence, join two short ones. Small changes add the bumpiness detectors read as human.
Rephrasing
Running AI text through a rewrite, by hand or with another tool, changes the pattern enough to lower the score.
Asking for a different style
Prompting the model to write in a looser, more varied voice produces text that is less even from the start.
What this means for you
A detector cannot be a reliable gate. Anyone who wants to pass, and knows to edit, usually can. So using a score as a hard rule, like an automatic fail, is unfair on two sides at once: it lets motivated people through, and it can still flag honest writers who did nothing.
It is still useful for what it is: a signal on raw, untouched text, and a first pass to decide what deserves a human look. Just not a verdict.
Why detection is losing the arms race
There is a deeper reason detectors will keep being easy to fool, and it is worth understanding. Detection and generation are locked in a race, and the two sides are not evenly matched.
Every time detectors get better at spotting smooth, even text, the models get better at writing with more variety and voice. Newer models already sound less robotic than older ones did, which erases the very tells detectors rely on. The target keeps moving, and it moves in the direction that makes detection harder.
So this is not a temporary gap that a better tool will close next year. The trend runs the other way. As AI writing gets more human, the line a detector is trying to draw gets fainter. Any strategy that depends on detection staying ahead is building on ground that is sliding out from under it.
The flip side: honest writers get caught in the middle
People usually ask “can detectors be fooled?” worried about cheaters slipping through. But the same weakness has a victim on the other side, and it is worth naming.
Because the tool only measures texture, a person who writes in a plain, even style can be flagged for work they did entirely themselves. So the detector fails twice: the motivated cheater edits their way past it, and the honest, plain writer gets caught by it. If you are worried about being wrongly flagged, the answer is the same one that protects everyone: keep your drafts and version history, and insist that any score be treated as a question, not a conclusion.
The honest takeaway
Treat detection like a smoke alarm, not a court. It can tell you something is worth checking. It cannot tell you what happened, and it can be silenced by anyone who knows how. Build your process around that, and you will use it well.