Replays & recording · Java · Intermediate

What Is Inside a ReplayMod .mcpr File? (recording.tmcpr & metaData.json)

A Minecraft replay file with the .mcpr extension is not a video file, nor is it a copy of your world save. Instead, it is a specialized ZIP archive that captures raw network traffic between the client and the server during your gameplay session. In this guide, we will dissect the internal files of a replay archive and inspect them safely in your browser using our Replay Viewer.

What you need

  • A Minecraft: Java Edition replay file (.mcpr) from your replay_recordings folder
  • Our browser-based Replay Viewer tool (processes files locally without uploading)
  • A backup copy of your .mcpr file before attempting any manual edits

Step by step

  1. 1Back Up Your Replay File

    Navigate to your Minecraft installation folder and open the replay_recordings directory. Locate the .mcpr file you want to examine and make a duplicate copy of it in a safe folder. Because .mcpr files rely on exact byte lengths and specific compression headers, an accidental change while poking around can render the replay unreadable by the game.

    Tip: If you ever see a .mcpr.tmp folder in your directory, that is an active or crashed recording that has not yet been zipped into a final .mcpr archive.

  2. 2Load the File into the Replay Viewer

    Open our Replay Viewer tool in your browser. Click the open file button or drag and drop your .mcpr archive directly onto the workspace. Because the tool runs locally in your browser, your replay file is parsed immediately in your device's memory without ever uploading to a server.

  3. 3Examine metaData.json

    In the Replay Viewer, inspect the metadata summary panel, which reads directly from the archive's internal metaData.json file. This plain-text JSON file contains human-readable information such as singleplayer (boolean), serverName, duration (in milliseconds), date (Unix timestamp), mcversion, fileFormatVersion, protocol (the numeric Minecraft network protocol version), and an array of player UUIDs. The game reads this small file first so it can display your replay list in the menu without unpacking the massive recording data.

    Tip: If you are unsure which numeric protocol corresponds to your Minecraft version, check the protocol field next to the mcversion string inside metaData.json.

  4. 4Inspect the Packet Stream (recording.tmcpr)

    Switch to the packet stream or timeline breakdown in the Replay Viewer to explore recording.tmcpr. This is the core binary file of the replay, containing every clientbound network packet—such as chunk data, entity movements, block changes, and chat messages—captured during the session. Each entry in the stream is prefixed by a timestamp in milliseconds and the byte length of the packet, allowing the playback engine to recreate the exact sequence of events.

    Tip: Adjacent to the main recording file, you will also see recording.tmcpr.crc32, a small checksum file used to verify that the packet stream was not corrupted during saving.

  5. 5Review Additional Archive Assets

    Check the archive contents list in the Replay Viewer for optional files that often accompany the core recording. You may see thumb, which is a raw image file used as the preview thumbnail in the replay selection screen, and mods.json, which lists the active mods required to render custom blocks or entities properly. If you have already edited camera paths in-game, you will also see timelines.json, which stores all your keyframe coordinates and time markers.

    Tip: If you want to inspect the raw JSON files manually outside the browser, you can rename your backup copy from .mcpr to .zip and extract it using your operating system's built-in archive extractor.

How it works

At the network level, Minecraft: Java Edition communicates using a stream of discrete packets—even in singleplayer, where the game runs an integrated local server. When you record a session, the recording mod intercepts every packet sent from the server to your client and writes it straight to disk inside recording.tmcpr. This explains why a replay only shows the chunks and entities that were loaded around you during gameplay; if the server never sent a chunk's packet to your client, that part of the world simply does not exist in the file.

The binary structure of recording.tmcpr is remarkably simple and sequential. Each recorded packet is preceded by two 32-bit big-endian integers: the first integer represents the time offset in milliseconds since the recording started, and the second integer specifies the exact length in bytes of the packet payload that follows. Immediately after those eight bytes sits the raw Minecraft protocol packet, starting with a VarInt packet ID and followed by its specific data fields.

Because Minecraft's network protocol changes between updates, packet IDs and data structures shift from version to version. That is why metaData.json stores the exact protocol number alongside fileFormatVersion. When you open a replay, the viewer or mod checks these numbers to load the matching packet definitions, ensuring that byte sequences for chunk sections, entity metadata, and player actions are translated accurately.

Common mistakes

  • Re-zipping the outer folder instead of the files inside: If you extract a .mcpr archive to edit metaData.json and then zip the parent folder instead of selecting the individual files directly, the game will fail to find metaData.json at the root of the archive.
  • Editing recording.tmcpr in a text editor: Opening and saving the binary packet stream in a standard text editor will corrupt the byte encodings and break the strict byte-length prefixes, making the entire replay unplayable.
  • Forgetting to update or remove the CRC32 checksum: If you intentionally modify the binary packet stream, the checksum stored in recording.tmcpr.crc32 will no longer match, causing integrity checks to fail.
  • Changing mcversion in metaData.json expecting cross-version compatibility: Simply typing a newer Minecraft version into the JSON file will not upgrade the replay, because the underlying binary packet IDs inside recording.tmcpr still follow the old network protocol.

FAQ

Why is my .mcpr file so much smaller than a normal video file or world backup?

Instead of storing millions of video pixels per second or every generated chunk in a world folder, a .mcpr file only records lightweight network instructions (like 'spawn creeper at X, Y, Z' or 'load chunk data') and relies on your game client to render the visuals during playback.

Can I convert a .mcpr file into a playable Minecraft world save?

Not directly from the file format alone, because recording.tmcpr only contains a stream of network packets for chunks you visited, rather than region (.mca) files, level.dat, or server-side container data for unopened chests.

What happens if a replay has no metaData.json inside it?

Usually this happens when Minecraft crashes while recording, leaving behind an unfinished recording before the final metadata and ZIP packaging step finishes; the Replay Viewer can help you inspect whether the raw recording.tmcpr packet stream is still intact.

A .mcpr replay file is a standard ZIP archive containing a binary stream of timestamped network packets (recording.tmcpr) paired with version and session details (metaData.json), all of which you can inspect safely in your browser using our Replay Viewer.

More replays & recording guides

Replays & recordingHow to Use the Replay Viewer to Debug Redstone Timings and Inspect PvP FightsWhether your complex piston door is breaking unpredictably or you lost a close multiplayer duel, standard real-time observation is often too fast to catch the root cause. The Replay Viewer on our site allows you to load recorded gameplay sessions directly in your browser—with zero file uploading—so you can step through events tick-by-tick and fly freely through walls. This guide covers how to locate your replay recordings, load them into the tool, and inspect game mechanics at the millisecond level.JavaIntermediate5 steps
Replays & recordingHow to Set Keyframes and Smooth Camera Paths in the Replay ViewerCreating smooth, cinematic flythroughs of your Minecraft Java Edition gameplay requires precise camera control and time manipulation. By using the browser-based Replay Viewer, you can plot position and time keyframes with spline interpolation to preview seamless camera paths. Because the tool runs entirely in your browser, your large recording files are processed locally and never upload to a server.JavaIntermediate5 steps
Replays & recordingHow Packet Replays Reconstruct World Chunks and Entities Over TimeMinecraft packet replays do not record raw video frames; instead, they capture the exact network protocol stream sent from the server to the client. By understanding how initial chunk data packets and subsequent block-change deltas interact, you can inspect and reconstruct the 3D world state at any exact millisecond. This guide explores the underlying packet architecture and shows you how to analyze it safely in your browser using the Replay Viewer.JavaAdvanced5 steps
Replays & recordingHow to Watch ReplayMod (.mcpr) Recordings in Your Browser with Replay ViewerReplay recordings allow you to relive your favorite Minecraft Java Edition moments, inspect builds in progress, or review multiplayer matches from any angle. Normally, watching these requires launching the full game client with specific mods installed. With our browser-based Replay Viewer, you can drop any .mcpr file directly into your browser to scrub the timeline, follow players, and fly around the recorded scene instantly without uploading your files anywhere.JavaBeginner4 steps