Overview
Minecraft Web Client supports loading worlds from multiple sources, including ZIP archives and local folders. All world formats compatible with Minecraft Java Edition work seamlessly.Worlds are loaded entirely in your browser using the integrated Flying Squid server and Prismarine Provider Anvil for region file handling.
Supported Formats
ZIP Files
- Entire world compressed in a single file
- Stored in browser RAM
- ~300 MB limit on iOS
- Read-only by default
Folders
- Native folder access via File System API
- Read-only or read-write mode
- Better for large worlds
- Chrome/Edge only
Loading Methods
Drag and Drop
The easiest way to load a world:Prepare Your World
Ensure your world is either:
- A ZIP file containing
level.datandregion/folder - A folder with standard Minecraft world structure
Select Mode (Folders Only)
For folders, choose:
- Read-only: Safe, no modifications to original files
- Read-write: Full editing capability, changes saved to folder
URL Parameters
- ZIP from URL
- Folder Structure (Advanced)
- Base64 Encoded
- Saved Worlds
Load a world from a ZIP file URL:Example CORS headers needed:
Via File System API
File Limits and Memory
ZIP Files
Desktop browsers: Can typically handle ZIP files up to several GB, depending on available RAM.
- Entire world is decompressed into memory
- Larger worlds = longer load times
- Consider using folder access for worlds >500 MB
Folder Access
No file size limits when using folder access:- Files read on-demand
- Only loaded chunks kept in memory
- Better performance for large worlds
Folder access requires the File System Access API, available in:
- Chrome 86+
- Edge 86+
- Not available in Firefox or Safari
World Structure
A valid Minecraft world folder must contain:level.dat Detection
Version Detection
The client automatically detects world version fromlevel.dat:
Version Override
Force a specific version:Exporting Worlds
Save your progress by exporting the world back to your computer.Export Command
Use the/export or /download command in chat:
Export to Folder
For folder-based saves with write access, worlds are automatically saved in place. Use the/export command to create a separate copy:
Saving Behavior
Automatic Saves
Worlds are automatically saved:- Every few minutes during gameplay
- On disconnect/world exit
- When using
/savecommand
For ZIP and URL-loaded worlds, use
/export to download changes. They’re saved to browser memory, not the original file.Disable Auto-Save
Prevent automatic saving:- Only manual
/savecommands work - No save on disconnect
- No periodic saves
- Useful for testing without cluttering browser storage
Read-Only vs Read-Write
- Read-Only Mode
- Read-Write Mode
Characteristics:
- Original files never modified
- Changes stored in browser memory
- Safe for preserving original worlds
- Use
/exportto save changes
- Exploring downloaded worlds
- Testing without risk
- iOS devices (no folder write access)
Compatibility Notes
Community Saves
Community Saves
Some community worlds use non-standard folder structures. The client automatically handles:This ensures worlds with custom folder mappings load correctly.
Version 1.8 and Earlier
Version 1.8 and Earlier
Worlds from Minecraft 1.8 and before don’t store version information in
level.dat.The client defaults to 1.8.8 but you should specify the correct version:Modded Worlds
Modded Worlds
Worlds from modded Minecraft may contain:
- Custom blocks (rendered as default textures)
- Mod-specific data (ignored)
- Non-standard chunk data (may cause errors)
Large Worlds
Large Worlds
For worlds larger than 1 GB:
- Use folder access instead of ZIP
- Increase render distance gradually
- Monitor browser memory usage
- Export frequently to prevent data loss
Debugging
Access world data in the browser console:See Global Variables for more debugging tools.
Best Practices
Backup Regularly
Use
/export frequently, especially before:- Major building projects
- Exploring new chunks
- Closing the browser
Version Consistency
Load worlds with their native version when possible:
Test Read-Only First
Always test with read-only mode before using read-write.
Monitor Memory
Watch browser memory usage for large worlds:
- Chrome: Task Manager (Shift+Esc)
- Firefox: about:memory
