Skip to content
Game save workbench
Local-first tools No installation Support status shown
DEVICE-LOCAL Favorites and recent pages stay in this browser.

Save File Formats

The Witcher 3: Wild Hunt Save File Format Reference

The Witcher 3: Wild Hunt save-file format reference covering the known PC file or folder pattern, documented format characteristics, compatibility boundaries, and what should not be inferred from an extension alone.

Editorial state
Reviewed
Reading time
3 min
Difficulty
Beginner
Last reviewed

Before you start

Work from a copied save rather than the live file. Use the documented path and filename/folder pattern to identify the correct record before inspecting bytes or text.

Key takeaways

What this guide establishes.

  • Use the documented save directory for the PC storefront/profile you actually play.
  • Back up the complete save boundary before restore, migration, repair, or editing.
  • Treat cloud synchronization as a separate copy that can overwrite a manual restore.
  • Do not infer editability from a filename extension; format and version compatibility must be verified.

The Witcher 3 keeps its Windows saves in one clear Documents directory, making a full-folder backup simple and preferable to selecting individual files. The folder can include many autosaves, checkpoints, manual saves, and preview images, so copying the entire directory preserves history. Modern releases also have cloud and cross-save features; those are useful for migration but they introduce conflict behavior, so a manual offline copy remains the best safety net before testing mods or tools.

Known The Witcher 3: Wild Hunt save-file structure

The researched filename or folder pattern is *.sav
*.png. File-extension context: .sav, .png The documented format notes are: The gamesaves directory contains .sav records and associated .png preview images. The save payload and screenshot are separate files.

Why an extension is not enough

A save filename can identify a likely container, but it does not prove the internal schema, game version, checksum rules, encryption state, or editability. Cross-save is a supported service feature, but a manual PC file copy should still be treated separately from account-backed cross-progression. SaveEditor therefore separates file identification from Tool compatibility and only labels a game-specific Tool Verified when its exact profile/version evidence passes the runtime gate.

Where the format is stored

PC save locations: Windows: %USERPROFILE%DocumentsThe Witcher 3gamesaves | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/292030/pfx/. Storefront context: Steam, GOG Galaxy, Epic Games Launcher, EA app. The local Documents path is shared across common Windows storefronts. REDlauncher can also participate in cross-progression services. This matters because two releases can use different containers or companion files even when the visible slot name is similar.

Back up before inspecting or editing

Copy the entire gamesaves directory so manual, automatic, checkpoint, and preview files remain together. A read-only viewer is lower risk than a writer, but the live save should still be copied first. Cloud context also matters: Steam, GOG, Epic, and EA cloud support are documented. The current game also supports cross-save with console versions through the supported account workflow. Keep the original bytes available so any experiment can be reversed without relying on a cloud service or automatic backup.

What this reference does not claim

This page does not infer an undocumented checksum algorithm, encryption key, compression layer, or cross-store conversion from the file extension. Troubleshooting evidence: If a restore seems to vanish, compare local and cloud timestamps and check whether the launcher synchronized a newer remote copy. Keep the backup outside the live Documents folder while testing. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.

Verification context: Windows/Steam Play save paths, .sav/.png files, storefront cloud support, and cross-save note were reviewed against current PCGamingWiki coverage.

Troubleshooting

If the expected result does not match.

Game-specific note: If a restore seems to vanish, compare local and cloud timestamps and check whether the launcher synchronized a newer remote copy. Keep the backup outside the live Documents folder while testing.

Verification and sources

How this guide was checked.

Phase 27 generated this Guide from the reviewed Phase 23/24 Game Hub evidence for The Witcher 3: Wild Hunt. The file/folder naming and documented format boundary were cross-checked against the same public references recorded on the Game Hub. No unsupported game-specific editor, checksum, encryption, or cross-platform conversion capability is implied.

  1. www.pcgamingwiki.com