
Rendering & screenshots · Java & Bedrock · Intermediate
How to Create a Base-Building Timelapse From Old World Backups
Turning your saved world backups into a smooth base-building timelapse lets you watch months of progress unfold in seconds. By using the World Renderer with locked camera coordinates and consistent bounding boxes, you can capture perfectly aligned frames across every snapshot. Because our tools run entirely in your browser, your world files are processed locally and never uploaded anywhere.
What you need
- A chronological series of world backups (Java world folders, .zip archives, or Bedrock .mcworld files).
- The approximate X, Y, and Z block coordinates of your base's final footprint.
- A local folder to store and number your exported image frames.
Step by step
1Organize and Verify Your Backups
Always keep a secure master copy of your backups before selecting or handling world files, even though the renderer only reads your data without modifying it. Gather your chronological backups into one folder and rename them sequentially (for example, 01_backup, 02_backup, 03_backup) so you process them in the exact order they were played. Verify that each Java backup contains its level.dat and region folder, or that each Bedrock backup has its level.dat and db folder.
Tip: Include an untouched backup from right before you started building to serve as the empty starting frame of your timelapse.
2Determine Your Final Bounding Box Using the Latest Backup
Open the World Renderer, click Open world folder or .zip, and select your most recent backup where the base is largest. Navigate to your base and define a 3D bounding box (minimum and maximum X, Y, and Z coordinates) that encompasses the entire finished build plus a small margin of surrounding terrain. Starting with the newest save ensures you do not accidentally choose a box that crops out structures or towers added in later stages.
Tip: If you are unsure of your base's exact coordinates, check your in-game coordinate display or look near the WorldSpawnX and WorldSpawnZ values listed in your level.dat file.
3Lock and Record Camera Coordinates and Lighting
While still viewing your latest backup in the World Renderer, position the 3D camera at an angle and distance that best showcases your build. Write down the exact numerical values for the bounding box (Min/Max X, Y, Z), camera position, camera target/rotation angles (pitch and yaw), zoom or field-of-view (FOV), and lighting or sun angle settings. Keeping these exact numbers identical across every backup is the core logic behind a jitter-free timelapse.
Tip: An isometric or high-angle 45-degree view usually shows vertical construction progress much better than a flat ground-level angle.
4Render and Export Each Backup Chronologically
Load your first backup (01_backup) into the World Renderer using Open world folder or .zip. Manually enter the exact bounding box coordinates, camera position, rotation angles, and lighting values you recorded in Step 3. Wait for all chunks within the bounding box to finish meshing, then export the rendered view as an image file named frame_001.png. Repeat this exact process for each chronological backup, incrementing the file number each time.
Tip: Never resize your browser window between renders, as changing the viewport aspect ratio can shift the framing and resolution of the exported images.
5Review Frame Alignment and Assemble
Open your folder of exported PNG images and flip through them rapidly using your operating system's default image viewer. Because the World Renderer applied the same spatial coordinates and projection matrix to every snapshot, the surrounding unedited terrain should remain completely stationary while your base grows block by block. You can now drop this numbered image sequence into any standard video editor or animated image maker to compile your final timelapse.
Tip: If one frame jumps or looks misaligned, re-open that specific backup in the World Renderer and double-check for a mistyped negative sign in the X or Z coordinates.
How it works
Both Java and Bedrock editions store worlds using a fixed global Cartesian coordinate system where every block occupies a specific integer (X, Y, Z) position that never drifts over time. In Java Edition, terrain is divided into 16x16x384 chunks stored inside Anvil .mca files within the region folder (or DIM-1 and DIM1 for the Nether and End). Each chunk section holds a Palette of block states and a packed BlockStates array. In Bedrock Edition, equivalent chunk data is stored as key-value pairs inside the db folder using LevelDB.
When you load a backup into the World Renderer, your browser reads only the specific chunk data intersecting your chosen X, Y, and Z bounding box directly in local memory. It translates the block state palettes and NBT data into a 3D mesh without uploading your files to a server.
A 3D camera view is mathematically defined by a view matrix (camera X, Y, Z position and target rotation) and a projection matrix (field of view and aspect ratio). By feeding the exact same bounding box and camera parameters into the renderer for every historical backup, each block is projected onto the exact same 2D pixel coordinate on your screen. Unchanged terrain pixels match identically from frame to frame, isolating only the blocks you placed or broke between backups.
Common mistakes
- Framing the camera using the earliest backup instead of the latest one, which often results in later expansions or tall roofs growing right outside the picture frame.
- Forgetting a negative sign on an X or Z coordinate when typing your bounding box or camera position, which shifts the render to a completely different part of the world.
- Resizing the browser window or toggling fullscreen mode mid-project, which alters the canvas resolution and causes frames to jump in size.
- Exporting the image before all chunks inside the bounding box have finished loading and meshing, leaving empty holes in the terrain for that single frame.
FAQ
What if some of my backups were saved in older game versions and others in newer ones?
Because Minecraft block coordinates do not shift across updates, your alignment will remain intact. The World Renderer reads the chunk format of each backup independently, even if older Java saves use the pre-1.18 Y=0 to 255 height limit and newer ones use Y=-64 to 320.
Why do some outer edges of my bounding box look empty in my earliest backups?
Minecraft only generates and saves chunks to disk when a player walks near them. In your earliest backups, you may not have explored the background areas yet, so those chunks simply do not exist in the region or db folder until later snapshots.
Can I create a timelapse of a Nether or End base?
Yes. After opening your world folder or .zip in the World Renderer, switch the active dimension to the Nether or the End before entering your recorded bounding box and camera coordinates.
By locking your bounding box and camera coordinates in the browser-based World Renderer across chronological backups, you can generate perfectly aligned frames to showcase your base's construction from start to finish.