Where are replay files stored in Beyond All Reason and how do you share them
If you just finished a close private match and want to show a friend the replay, here is the part that trips people up: you cannot send a link to a replay that happened inside a private game. The replay exists as a file on your machine. You have to find it and share the file directly.
Bars: replay, file location, sharing
Why private match replays do not have shareable links
Public lobby matches sometimes generate links the community tools can resolve. Private matches are different. The game records a replay file locally and never uploads it anywhere. When someone asks for a link, the answer is straightforward. There is no link. You need the actual replay file from the Data to demos folder in your BAR installation.
This catches a lot of newer players off guard. They finish a good game, copy the replay ID or match name into chat, and wonder why nothing happens. The replay is sitting on disk, not on a server. Moving the file from your machine to a friend or a mentor review thread is the only way to share it.
How to find your replay files
Follow these steps to locate replay files from private matches:
- Open your BAR installation directory. This is wherever you installed the game through the lobby.
- Navigate to the Data folder inside the installation directory.
- Open the demos subfolder. This is where all recorded matches, including private ones, get saved automatically.
- Sort by date. The most recent match will be at the top. Files carry a timestamp so you can identify which one is the right game.
Each file in the demos folder has a .sdz extension. That is the replay file format BAR uses. Do not rename or rename the extension. The game reads these files from this specific folder and if you move them somewhere else, the replay browser will not see them.
How to share a replay file with someone else
Once you have the .sdz file, sharing works like any other file:
- Direct message: Send the .sdz file through whatever chat platform you use with your team or community.
- Cloud storage: Drop it into a shared drive folder if your team has one. This works well for organized groups that review replays regularly.
- Community upload: Some community spaces accept replay file uploads for mentor review. Check the relevant channel or thread for format requirements.
The person receiving the file needs to place it in their own Data to demos folder to watch it in-game. They can also open it directly from the file by double-clicking if BAR is set as the default handler for .sdz files.
Common replay mistakes players make
A few recurring problems players run into when trying to work with replays:
- Sending lobby IDs instead of files: The lobby match ID or room name does not let anyone access the replay. Only the .sdz file works.
- Replay not showing up in demos: Make sure the recording option was enabled before the match started. If recording was off, there is no file to find.
- Game updates breaking old replays: If the game has been patched since the replay was recorded, it may no longer load. This is a common issue with older replay files. Always share replays soon after the match before patches shift things.
- Corrupted or incomplete files: If a game crashed or the lobby host disconnected unexpectedly, the replay file may be incomplete. These will not load properly.
Using replays to get better
Once you can find and share replays reliably, they become your fastest improvement tool. Watch your own games back and you spot mistakes you were blind to in the moment. Mexes you forgot to build. Scouts you did not send. Air you did not answer. Things show up on replay that you simply miss when you are playing.
A practical approach works best. Pick one focus area for each replay review. Check your first three minutes of economy. Look at whether you scouted. See if your unit composition made sense against what your opponent built. That single question per replay beats general browsing every time.
If you share the replay and ask a focused question when seeking feedback, you get better answers too. Instead of asking someone to check your game overall, ask about your opening mex count or your scout timing. Specific questions get specific useful answers.
Eco scaling and early timing context
While reviewing replays, two patterns tend to show up in team games that newer players overlook. The first is economy scaling speed. In a five player commander match, T2 units can appear as early as two and a half minutes into the game. That means your opening needs to account for very fast tech transitions, not just steady T1 play.
The second pattern is faction economy behavior. Some factions scale more easily because their T1 mex extractors carry no upkeep cost, meaning each new mex is pure income rather than a trade-off against existing production. Players who understand this early can push economy advantages faster and stay ahead on resources. The faction advantage in early economics shows up clearly in replay timelines if you watch the resource graphs.
Keep sharing and learning together
The ability to find and share replay files is a small thing that opens up a lot of improvement. Teams that review replays together get coordinated faster than teams that just queue the next match. The habit of watching your own games back and asking for focused feedback is what separates players who plateau from players who keep climbing.
If you are looking for a group that takes this seriously without the drama, Creed of Champions runs regular coordinated sessions where players share replays, give constructive feedback, and focus on actual improvement. The attitude is simple: everyone is here to get better, nobody gets yelled at for missing something, and teamwork carries every game. As one member put it:
Creed of Champions is a great place to learn and play BAR in a friendly atmosphere. Training sessions, team gameplay, even some non-BAR stuff. Large cross section of abilities, time zones, and game mode interests.
[Crd] Cleaned testimonial
Drop a replay. Ask your question. Learn from the answer. That is the loop that works.