What’s actually inside the db folder
Open a Bedrock world save and you’ll see level.dat, levelname.txt, and a db folder in the root directory. This db folder is the body of Bedrock world data itself—inside it is a LevelDB key-value database, made up of several .ldb/.ldat data files, a MANIFEST, a CURRENT, and logs (.log).
LevelDB stores all the real world content as “key → value” pairs:
- Chunks and blocks (each chunk is stored with its coordinates as the key)
- Entities (mobs, items, minecarts, and so on)
- Container contents (items inside chests and shulker boxes)
- Villager trades, game state, and other runtime data
In other words, almost everything you build in the world ends up in db/.
How it divides labor with level.dat
It’s easy to confuse db/ with level.dat, but the two have clearly separate jobs: level.dat is metadata (what the world is called, what mode it’s in, what seed it uses), while db/ is content (what the world looks like). This also differs from Java Edition—Java stores chunks in .mca files under region/, whereas Bedrock packs everything into a single LevelDB database. To find out where all your saves are, see where Minecraft saves are stored.
Don’t edit it by hand—diagnose corruption first
Because it’s a database format, the files in db/ reference one another and come with indexes and logs, so editing or deleting them by hand very easily breaks consistency: at best some chunks turn empty and holes appear in the terrain, at worst the world simply won’t open. If your world shows missing chunks or loading errors, the safer approach is to use mcworld.app’s free on-device diagnosis to read out a health report, then decide whether to go with a free simple repair or a pay-per-result advanced repair. The whole process never overwrites your original file—each run produces a new version while keeping the original and its hash for traceability, paid jobs that fail are automatically refunded, and there’s no promise of 100% recovery. Further reading: what to do when an .mcworld file is corrupted.