Tennis point-by-point string to score converter
Paste a tennis point-by-point string such as SSAS;RSRRR;SDSSS. You get the score after every point, the final score and the matching fields of our Score object.
The converter runs in your browser and needs JavaScript. Without it, this page shows the example from the notation page worked out below.
Score after the last point
- Sets
- 0-0
- Games in the set
- 3-0
- Points in the game
- 0-0
- Serves next
- Player 2
Score: 3-0. Player 2 serves next.
Score object fields
{
"sets": [0, 0],
"games": [[3], [0]],
"points": ["0", "0"],
"server": 2,
"is_tiebreak": false
}
The same fields as the Score object in our API. After the last point of a match, server stays on the player who served that point, as our stored match rows do.
| # | Code | Won by | Score after | Serves next |
|---|---|---|---|---|
| 1 | S | P1 | 0-0, 15-0 | P1 |
| 2 | S | P1 | 0-0, 30-0 | P1 |
| 3 | A | P1 | 0-0, 40-0 | P1 |
| 4 | S | P1 | 1-0 | P2 |
| 5 | R | P1 | 1-0, 15-0 | P2 |
| 6 | S | P2 | 1-0, 15-15 | P2 |
| 7 | R | P1 | 1-0, 30-15 | P2 |
| 8 | R | P1 | 1-0, 40-15 | P2 |
| 9 | R | P1 | 2-0 | P1 |
| 10 | S | P1 | 2-0, 15-0 | P1 |
| 11 | D | P2 | 2-0, 15-15 | P1 |
| 12 | S | P1 | 2-0, 30-15 | P1 |
| 13 | S | P1 | 2-0, 40-15 | P1 |
| 14 | S | P1 | 3-0 | P2 |
P1 and P2 are player 1 and player 2. Every score reads player 1 first. A bold score ends a game.
The converter works in your browser and sends nothing. The box and the result are marked so the site analytics skip them.
Get a free API keyCompare score notation formats
How does the example string read?
The notation page gives SSAS;RSRRR;SDSSS as its example. With player 1 serving first, player 1 holds, breaks and holds again, so the first set stands at 3-0 after 14 points. Player 2 serves next.
Which rules does the converter read?
Exactly the ones our notation formats page lists for point-by-point strings.
- S means the server won the point and A is an ace. R means the returner won it and D is a double fault.
- Each code is relative to the server. Who served first is a separate value, so you choose it above.
- A semicolon ends a game and a full stop ends a set.
- A slash shows each change of server inside a tie-break.
- A string can stop anywhere. The example ends after a game with no mark after it.
The converter marks the first character that breaks one of these rules or the score. The table stops at the last point before it.
How does it keep score?
The string marks games and sets. The score inside them follows the ITF Rules of Tennis 2026, as our tennis data glossary explains them.
- A game goes to the first to four points with a two-point lead (Rule 5a). Points read 0, 15, 30, 40 and AD.
- At six games all a tie-break starts. The player whose turn it is serves one point, then each serves two in turn (Rule 5b).
- A set goes to the first to six games with a two-game lead, or to the tie-break (Rule 6). Best of three needs two sets and best of five needs three (Rule 7).
- A double fault loses the point for the server (Rule 24a).
- A final set can end in a tie-break to 10 at six games all. The Grand Slams play it that way (Grand Slam Rule Book 2026, Article I.L). It can also have no tie-break, so it runs until one player leads by two games.
What does the converter not read?
Where the notation page does not say how something is written, the converter stops and says so. It does not guess.
- A match tie-break in place of a final set. The notation page lists it as not specified.
- A semicolon straight before the full stop that ends a set. Put the full stop right after the last point of the set.
- Games with no advantage, where the point at deuce decides the game.
- Lower-case codes and spaces inside the string. Spaces and line breaks at either end are ignored.
How do the fields match our API?
The object under the result holds five fields of the Score object our REST API and WebSocket feed send. Their shapes come from our published OpenAPI document.
setscounts the sets each player has won.gamesis[games_p1, games_p2], with one entry per set. A new set starts at 0.pointsholds strings such as "15" and "AD". In a tie-break it holds the running count, andgamesstays at six all until the tie-break ends.serveris 1 or 2 for the player who serves next. After match point it stays on the player who served it.is_tiebreakis true while a tie-break is the game in play.
Need strings to test with? Our mock tennis data generator plays random matches through this parser and writes each played match in this notation.
Checked against the notation page and the OpenAPI document on 17 November 2026.