Press the player who won the point, not the player who is losing, and the tennis score stays correct from Love to match point. A tennis scorekeeper is built to handle the part of tennis scoring that ordinary counters cannot: the sequence Love, 15, 30, 40, Deuce, Advantage, game, six games to a set, and the first-to-seven tie-break at six games all. Almost every error that occurs while using a tennis scorekeeper comes from the user trying to do one of those transitions in their head, tapping the wrong side, or skipping a control that exists specifically to reverse a slip. The fix is not more math; it is a small set of habits that keep the tool's local state machine in charge of the score and keep you in charge of confirming the right player won each point. The Tennis Scorekeeper applies the standard game and tie-break transitions for you, so most mistakes are preventable with a few deliberate clicks before and during the match.
What Usually Goes Wrong in a Tennis Scorekeeper
Most scoring errors come from a handful of predictable actions. The first is tapping the player who just lost a long rally, because it feels natural to record "the loser" when the shot went long. The second is trying to figure out the score yourself and then tapping only when the visible number does not match what you expected. The third is starting a new match without realizing the previous point history is still attached to the local day. The fourth is treating the scorekeeper like an umpire and waiting for it to track service order or doubles rotation, which it does not handle.
The tool is intentionally limited to standard singles scoring, so a misuse mistake looks like expecting features that were never part of the design. Knowing that boundary prevents the second category of error: confusing a personal aid with a tournament scorecard. As soon as you stop asking the tool to do things it was never meant to do, the actual scoring mistakes become very small.
Set Up the Match Correctly Before the First Point
The cheapest mistake to avoid is the one that happens before the match starts. Enter both player names before recording any point. If a name is left blank or misspelled, the export files will still work, but you lose the easy way to read who is who at a glance, especially during a long match when the screen scrolled past the player labels. If you play left-handed versus right-handed or just want a clear visual order, take the few seconds to confirm the left-side player is the left tap target.
Decide before the first serve whether the match is best-of-three sets with a tie-break at six games all, which is the format the scorekeeper supports. If your club or ladder uses a different format, such as a match tie-break in place of a third set, or no-ad scoring, do not use this tool to score it; the state machine will silently apply the standard rules and your final set score will not match the real result. The deuce and advantage logic is fully implemented, so once you confirm the format is standard, the scorekeeper will not surprise you with a wrong transition.
Record Points the Right Way
The exact sequence to keep a tennis match score accurate from the first point to match point.
- Type the name of player A in the first name field and the name of player B in the second name field.
- Watch the point end and identify which player won the rally, not which player made the error.
- Tap the button or row under the player who won the point; the scorekeeper updates sets, games, and the game score together.
- Glance at the updated score and read it back silently, e.g. "30-15, player A" to confirm the transition matches what you saw.
- If the displayed score does not match the rally, tap Undo last point immediately, before tapping anything else.
- Continue one point at a time, never batching two points into one tap; the state machine is designed around a single point per tap.
- At six games all, expect the scorekeeper to switch the set view to a numeric tie-break that runs to seven points by two.
- When the second set is won by either player, expect the match to end and a Start new match control to appear.
Handle Deuce, Advantage, and the 6-6 Tie-Break Safely
The transitions that feel like the scorekeeper is "doing too much" are the ones most worth trusting. At 40-all, the scorekeeper stops showing 40 and starts showing Deuce. The next point becomes Advantage for the side that won it. A second point in a row for that side ends the game; a point for the other side returns the game to Deuce. None of those words are user input. They are the output of the local state machine following the ITF and USTA definitions of a standard game.
| Game score after the point | What the scorekeeper should display | What to do next |
|---|---|---|
| 0-0 | Love-Love | Continue tapping the winner of each point. |
| 1-0, 2-0, 3-0 | 15, 30, 40 | Continue tapping the winner of each point. |
| 3-3 | Deuce | Tap the next winner; the score will become Advantage for that side. |
| Advantage A or B | Advantage side named | If the same side wins the next point, the game ends; if the other side wins, the game returns to Deuce. |
| 6-6 in games | Tie-break to 7, win by 2 | Treat the points as numeric. The set is awarded at 7-6 when the tie-break ends. |
If the screen shows something that does not match this table, the most likely cause is an earlier wrong tap that has not been undone yet. Do not try to "catch up" by tapping the side that fixes the display; undo back to the last correct state and replay the missed point. The tie-break in particular is unforgiving if it gets out of sync, because every subsequent point is interpreted relative to a base that may already be wrong.
Undo, Start New Match, and Clear History Without Regret
The three reset controls do very different things, and confusing them is a common mistake. Undo last point restores the full previous match snapshot, including the state across a game boundary, a set boundary, or a tie-break. It is safe to use after any single tap and will not corrupt the score. Start new match clears only the active match score while keeping the local daily point history that has already been recorded against your browser. Clear local history removes that stored daily record entirely, which is useful when you want to start over from a blank browser state but is the wrong choice if you still need yesterday's practice total.
The rule of thumb is to use Undo the moment a tap looks wrong, even if the visible score still seems plausible. Tapping "just one more time" to compensate for a wrong tap is the single fastest way to drift away from the actual score, because the state machine keeps applying standard transitions on top of an already-wrong base.
Export and Share Without Leaking Player Names
Export only when you actually need a file outside this browser. The CSV export produces a Date and Points recorded file that opens cleanly in any spreadsheet and is the right choice for an archive of how many points you logged on a given day. The PNG export creates a 1080 by 1350 image showing the total and the recent days; the image deliberately does not include a URL or the player names, which limits personal context if you share the picture in a group chat or lesson recap. Both exports are produced locally with browser Blob and canvas APIs, so the file is generated on your device rather than uploaded to a service. If browser storage is unavailable, the score can still be used on the current page, but the tool will disclose that it cannot retain history between sessions, so export before closing the tab if you want a record.