Tiny Witch

A Practical Guide to Tiny Witch and Why It Still Matters

I first ran into Tiny Witch back when I was trying to fix a corrupted save file that had been silently eating quest progress over several play sessions. Most tools at the time were bloated with features nobody needed. Tiny Witch did exactly one thing and did it cleanly, so I kept coming back to it. It's a lightweight save editor and utility tool for The Witcher 3, designed to let you modify game files without carrying the overhead of heavier alternatives. The interface is basically a single window with your save slots on the left and the data tree on the right. You open a save, navigate to the section you need, change the value, and save it out. That's it. No wizards, no installers, no telemetry. I've been doing this for years and the workflow has never changed much. There's a learning curve if you've never touched a hex editor, but the tool itself doesn't make you write hexadecimal manually. You're working at a higher level most of the time.

Tiny Witch: What It Actually Does

At its core, Tiny Witch parses the save game format used by The Witcher 3 and lets you read and write individual fields. The Witcher 3 save format is based on a modified version of the Crystal Dynamics format, which itself traces back to the Gamebryo engine structure. Understanding that helps a lot because it means certain fields are always at predictable offsets, and the tool maps those for you rather than making you reverse-engineer each one from scratch. The main use cases are straightforward. You want to change your gold amount. You want to adjust skill points that got lost after a patch. You want to flag quests as completed without grinding through them. You want to pull gear out of a save from a previous account. All of these work inside Tiny Witch without needing to touch the actual game executable or run any injectors. I also use it when I'm setting up specific challenge runs and need to strip inventory or reset levels. It's faster than starting a new game and slower than a trainer because you're editing real save data, which means the game doesn't flag anything. That distinction matters more than people realize.

Here is the part nobody warns you about though. Tiny Witch reads the save format as it existed at a certain patch level. CD Projekt Red changed serialization details in the Blood and Wine expansion and again in the next-gen update, so a save from the next-gen version doesn't always parse cleanly in the current Tiny Witch build. I spent about forty-five minutes one evening trying to figure out why every field was showing as null, only to realize the save was from version 4.04. You have to match the tool to the patch version of your save, or convert the save first using the older format bridge that some community members maintain.

Getting It Running and Using It Without Breaking Things

Download the latest release from the official thread. The tool is portable, which means no installer, no registry entries, no service running in the background. Just extract it and open TinyWitch.exe. It looks for your save files in the standard location under Documents by default, but you can point it elsewhere if you keep saves in a cloud folder or a separate drive. When you load a save, the left panel shows your slots. Click one and the right panel opens the data tree. The tree is organized by category: player state, quests, inventory, skills, locations. Each category expands into sub-fields. Most values are readable as decimal numbers. Some are flags stored as bitmasks, which the tool displays as individual checkboxes rather than a raw integer. This is actually helpful because a bitmask like quest completion is easier to toggle correctly when you can see each flag separately instead of guessing which bit corresponds to which quest. Editing a field works the same way everywhere. Click the value, type the new number, press Enter. The change sits in memory until you write it out. You need to explicitly save after editing, or the tool won't write anything. This is by design, not a bug. It prevents accidental overwrites of your original file.

Before you save anything, copy your original save file. Seriously. The Witcher 3 saves are not trivial to recover if they break, and the game doesn't keep enough rollback versions to be safe. I keep a backup folder with a date stamp on each copy. Takes thirty seconds and has saved me twice already when a bitmask edit went wrong and corrupted a quest flag in a way that soft-locked a side quest.

Where Tiny Witch Falls Apart

The tool is stable, but it is not comprehensive. There are save fields it cannot parse, mostly because CD Projekt Red added new data structures in patches that the current version doesn't recognize. If you edit a field that exists in a newer save format but isn't mapped in Tiny Witch, the tool will either show a blank value or skip the field entirely. Your save might still load, but the edited portion won't have taken effect, and you'll waste time wondering why the change didn't stick. Multiplayer is not a factor here since The Witcher 3 is single-player, but online-verified saves from cloud sync can create a timing issue. If you edit a save while the game is syncing it to the cloud, you can end up with a merged file that has partial data from both the old and new versions. The game may refuse to load it or may load it with corruption in the affected sectors. Always close the game and pause any cloud sync before editing. The next-gen update introduced additional checksums on some save structures. Tiny Witch does not currently bypass those. If you edit a field that is checksummed, the save may appear to load but then the game silently reverts the change or crashes during a specific scene. This is one of the more frustrating edge cases. The workaround I use is to identify which fields are likely checksummed by testing edits on a copy save first, then only applying changes to fields that don't trigger the checksum on the original. It's slow, but it prevents corruption of your main playthrough.

A Few Things Beginners Miss

The first thing people get wrong is assuming that all numeric fields behave the same way. Some values use fixed-point arithmetic rather than plain integers. If you see a value that looks wildly too large or too small, check whether the field description indicates fixed-point. Editing a fixed-point value as a regular integer will produce garbage in the game. The second thing is the relationship between quest flags and quest states. A quest in The Witcher 3 has multiple layers: whether it's active, whether it's completed, whether it's failed, and whether certain stages are flagged as done. Setting a quest to completed without also setting the correct stage flags can leave the quest in a limbo state where it shows as done in one menu but not another. Always set the full state, not just the completion flag. Inventory items have a dependency on equipment slots. If you add a weapon without ensuring the character has the required strength stat or skill level, the game may remove the item on the next load or place it in a disabled state. I learned this the hard way when I gave a high-tier sword to a starting-level character and spent an hour trying to figure out why it disappeared every time I loaded the save.

Alternatives When Tiny Witch Isn't Enough

If you need features beyond what Tiny Witch offers, like mass-editing multiple saves at once, running batch transforms, or working with the newer next-gen save format directly, you might look at W3Edit or the broader community tools built on top of the open save format documentation. Those tools are heavier and have a steeper setup curve, but they cover more ground. Tiny Witch fills the gap for people who want something fast and focused without downloading a full toolkit. For simple gold or skill point edits, Tiny Witch is usually faster than any alternative. The process from opening a save to writing the change typically takes under two minutes. The only real time cost is learning the data tree structure, which settles after the first few sessions. Once you know where the player state section is and how to navigate to skill trees, the tool becomes nearly reflexive. I still reach for Tiny Witch when I need a quick edit and don't want to dig into a larger toolchain. It hasn't been updated to match every patch, and that's the main limitation. But for the saves and scenarios it does support, it remains one of the most reliable options available.