What this game keeps between visits
Does Brick Breaker Save Your Progress? High Scores and Game Sessions Explained
The Brick Breaker game on this website remembers a personal high score in the browser, but it does not save an in-progress run. Your best score and your current game are different kinds of data: one is stored locally, while the other exists only while the game is running.
What is saved—and what is not?
This summary describes the current BrickBreaker.online game implementation. It is an independent browser game, not Google Block Breaker, and the details below do not apply to other Brick Breaker games.
| Game information | What happens |
|---|---|
| Personal high score | Stored in this browser's local storage when the game records a new best. |
| Current score | Held during the active run; not saved as a resume point. |
| Current level and lives | Held in the running game; not restored as session progress after a reload. |
| Account or cloud sync | The project code does not connect the high score to an account or a sync service. |
How the personal high score is saved
When the game starts, it reads the stored high-score value from browser local storage. If it cannot read a usable value, the source code falls back to zero. During play, the score in the current run is compared with that personal best at specific checkpoints. If the run has beaten the stored score, the new value is written back to local storage.
The game checks for a new high score when the ball is lost, when a level is cleared, and when the final level is completed. It does not write a new record after every brick hit. That means a score earned since the last checkpoint may not yet be stored if the page closes before another checkpoint happens.
The browser-storage calls are wrapped in error handling. If the browser refuses a read, the game starts with a high score of zero; if it refuses a write, the game continues but the new record may not persist. The interface does not show a separate save confirmation.
Does the game resume after a refresh or closed tab?
No saved session is loaded. The current score, level, remaining lives, ball position, and brick layout are held in the game engine's in-memory state. Starting a new game also resets the run to Level 1 with a fresh score and lives. The code does not write a checkpoint that can restore those details after a page refresh or a later visit.
The source uses local storage for the personal high score. It does not use session storage, IndexedDB, cookies, or a remote score service to save a run. So a visible best score can remain while the current attempt is gone.
Will the high score appear on another device?
The game does not sync records through an account. Its stored value is kept by the browser on the device where you played, so do not expect the same high score to appear automatically in another browser or on another device. Clearing browser site data can also remove locally stored values.
For the quick answer within our browser-access guide, see the FAQ about whether a high score follows you to another device. To review how points are earned during a round, read our rules and scoring guide.
Frequently asked questions
Does Brick Breaker save my current level?
No. The game does not store the active level as a resume point. The level resets when a new game starts.
When does the game save a new high score?
It checks and writes a new best after a lost ball, a cleared level, or completion of the final level, provided the score is higher than the previous best.
Does restarting erase my personal best?
Restarting resets the current run's score, level, and lives. It does not intentionally clear the locally stored high score.
Is this the same as Google Block Breaker?
No. This page describes BrickBreaker.online's independent game. It does not describe Google's separate Search game or its storage behavior.