One Life
The first wrong character ends the attempt immediately, so the score is nothing but distance — how many characters you reached before a single mistake closed it out.
QWERTY layout assumed. Backspace corrects; uncorrected errors count against net WPM.
One Life gives you a fresh two-hundred-word passage every time you play, and exactly one rule: the moment a typed character doesn't match the one it's supposed to, the attempt is over. Not counted against you and continued, not flagged for a later fix — over, on the spot. The HUD reports how many characters you reached as 'Survived,' and a 'Lives' indicator that reads one until the instant it reads zero.
Every other test and most other games on this site let a mistake happen and move past it, whether it's corrected with backspace or left in the finished text as a penalty. One Life removes that middle ground entirely. There's no such thing as a corrected error here, because the one error you're allowed to make also ends the game in the same keystroke — backspace never gets a chance to matter, since by the time you'd reach for it, the run has already stopped.
That single rule inverts the incentive every other page on this site runs on. Normally, a bit more speed is worth a bit more risk, because an error costs you a WPM penalty and nothing more. Here, an error costs you the entire rest of the passage, whatever that would have been worth. Once a mistake caps your score outright instead of just denting it, the highest-scoring choice is often to type well under your comfortable pace, especially heading into an unfamiliar word — trading speed you'd barely notice losing for a mistake you can't afford to make.
How to Play
Type the passage as it appears; each correct character advances you and adds to your Survived count. The moment a character doesn't match, that character is still added to your total — meaning your final Survived number includes the position of your own mistake, not just everything that came safely before it — and the attempt ends there. A new two-hundred-word passage is generated for every attempt, so you're never memorising or replaying the same text twice in a row.
Because the passage regenerates each time, your Survived count isn't directly comparable attempt to attempt the way it would be on a fixed passage — a run that ends early might have hit an awkward double letter or an uncommon word third in, while a longer run might simply have opened with easier words. A single run says less about your typing than several runs stacked side by side, since some of what decides where you stop is which specific words happened to come up, not just how carefully you typed them.
When the run ends, Survived carries straight onto the results screen with you, sitting next to the standard net WPM, gross WPM and accuracy figures rather than being swallowed by them. That matters more here than it would elsewhere, because accuracy alone tends to read misleadingly high: most attempts end on a single wrong character inside an otherwise clean run, so Survived, not accuracy, is the number that actually reflects what this game measures.
Why Backspace Never Comes Up
On a standard test, backspace exists precisely because a mistake and its correction are two separate moments — you notice, then you fix. One Life collapses those into a single moment: the mistake is also the end of the attempt, so there's never a window where an error is sitting there waiting to be corrected. The key isn't disabled, the way it is on the No-Backspace Typing Test; it simply never has anything to do, because nothing survives long enough to need fixing.
The Mistake Itself Counts Toward Your Total
Here is exactly what 'Survived' counts: the character that ends your run, not only the ones before it. Reach position two hundred and one before the wrong keystroke lands, and your Survived figure reads two hundred and one, not two hundred. It's a small distinction, but it means the reported number includes the step that ended things, rather than strictly counting only what you got right.
Slower Wins Once One Mistake Is Final
On a timed test, easing off costs you a few WPM you'll likely earn back somewhere else in the run. Here, easing off into a word you're not confident about costs you nothing if it's right, and saves you the entire remainder of the passage if it would otherwise have been wrong. That asymmetry is why the highest-scoring pace in this format usually sits noticeably below a comfortable one — the Accuracy Focus: Deliberately Slowing Down lesson makes a similar case for ordinary practice, but here the incentive isn't a suggestion, it's built into how the score is decided.
What Actually Ends Most Runs
In practice, a lot of runs here don't end on a hard word — they end on a double letter or a repeated pair that the fingers commit to before the eyes catch up, the same kind of slip the Double-Letter Drill targets directly. Since there's no room to recover from that specific habit here the way there is on an ordinary test, One Life tends to surface it faster and more bluntly than a passage where the same mistake would cost only a fraction of a WPM.
Frequently Asked Questions
Why is typing slower than usual actually the better strategy here?
Because one mistake ends the run outright rather than just costing a small WPM penalty, the extra speed you'd gain from pushing your normal pace is rarely worth the risk of losing the entire rest of the passage. Easing off, especially into an unfamiliar word, usually raises your expected Survived count even though it lowers your instantaneous speed.
Does backspace do anything at all in this mode?
It's available, but it never comes into play, since the only mistake you'll ever make in a run also ends that run in the same instant — there's no interval where an error is sitting there waiting to be backspaced.
Is the passage the same every time, like it is on Ghost Race?
No. Ghost Race reuses one fixed forty-five-word passage so attempts compare cleanly; One Life generates a fresh two-hundred-word passage every time, which means your Survived count is shaped partly by which words happened to come up, not only by how you typed them.
How is this different from the No-Backspace test, where mistakes also can't be undone?
On the No-Backspace Typing Test, an uncorrected mistake stays in your finished text as a permanent mark, but the test keeps running to the clock regardless. Here, that same kind of mistake doesn't just stay uncorrected — it ends the attempt immediately, with nothing typed after it.
What does the final results screen actually show once a run ends?
Net WPM, gross WPM and accuracy still show up exactly as they do everywhere else, but Survived joins them now as its own figure rather than being left behind on the HUD. Because most runs here end on one wrong character inside an otherwise correct stretch, accuracy alone won't tell you much — Survived is the number worth reading first.