Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Format:Unreal Engine SaveGame (GVAS)

From ReverseEngineering.wiki
Format
Vendor Epic Games
Magic GVAS (47 56 41 53)
Extensions .sav
Endianness little-endian
On this wiki Facts · Code · Notes · Topics

Save files written by Unreal Engine's USaveGameSystem (.sav): the magic GVAS, a version header (save game version, package version, engine version, custom versions), the save game class path and a stream of tagged properties ending with the name None.

Overview

Unreal Engine games that use UGameplayStatics::SaveGameToSlot write a binary file that starts with the four bytes GVAS. The body is the engine's tagged property serialization of one UObject (the SaveGame subclass), so every value carries its name and type name. This is why GVAS files can be read without the game: the open-source reader uesave-rs (see Code & repositories) parses them generically. Many games add their own wrapper (compression, encryption) around it; check the first four bytes before assuming.

Header

All integers little-endian (read from uesave Header::read in uesave/src/lib.rs):

  1. magic u32 GVAS; uesave only warns on a different magic and continues.
  2. save game version u32. Values 3 and above (except 34, which uesave suspects is game specific) add a second package version field.
  3. package file version UE4 u32; then, when the save game version is >= 3 and not 34, package file version UE5 u32.
  4. engine version: major u16, minor u16, patch u16, build u32, then a branch string.
  5. custom version format u32, then a u32 count and that many entries of a 16-byte GUID plus i32 value (only when the engine version is >= 4.12).

Strings (FString) are an i32 length followed by the bytes including the terminating NUL; a negative length means UTF-16 with -length code units. An empty string is length 0.

Body

After the header comes the save game class path as an FString, then (engine 5.4 and later only) one extra byte, then properties until a property named None.

Before engine 5.4 a property tag is: name FString, type-name FString (IntProperty, Int8/16/64Property, UInt8/16/32/64Property, FloatProperty, DoubleProperty, BoolProperty, ByteProperty, EnumProperty, StrProperty, NameProperty, TextProperty, ObjectProperty, InterfaceProperty, SoftObjectProperty, FieldPathProperty, the delegate types, ArrayProperty, SetProperty, MapProperty, StructProperty), size u32, array index u32, then type-specific tag data (enum name for ByteProperty/EnumProperty, the value for BoolProperty, inner type names for arrays, sets and maps, struct type for structs) and the value of size bytes. Engine >= 4.12 also has an optional property GUID in the tag.

From engine 5.4 (PROPERTY_TAG_COMPLETE_TYPE_NAME in uesave) the type is a tree of names each followed by a child count, then a flags byte (array index, property GUID, extensions, binary/native serialize), so the layout differs.

Details settled against uesave lib.rs at 1917a22ab6 (facts: Fact:Unreal Engine SaveGame (GVAS)/behavior/Pre-5.4 property tag fields, Fact:Unreal Engine SaveGame (GVAS)/enum/EPropertyTagFlags):

  • Pre-5.4 tag extras: a BoolProperty has its value as one byte in the tag and an empty body; ByteProperty and EnumProperty carry the enum name ("None" means a plain byte); StructProperty carries the struct name and a 16-byte GUID; ArrayProperty and SetProperty carry the inner type name; MapProperty carries the key and the value type names. After these, from engine 4.12, comes a byte and, if non-zero, a 16-byte property GUID.
  • Arrays of structs begin with the count, then (4.12 to 5.3) one inner tag naming the struct, then the elements. Set and Map tags never name the struct types of their keys and values, so a generic reader needs a schema for them.
  • From 5.4 the tag is: name, a type tree (each node an FString plus a u32 child count: StructProperty has the struct path as a child plus an optional GUID, MapProperty has key and value types, EnumProperty has the enum path and the underlying type), size u32, one flags byte (0x01 array index follows, 0x02 property GUID follows, 0x04 extensions, 0x08 binary/native serialize, 0x10 the bool is true), then the optional index and GUID.

Code & repositories

  • https://github.com/trumank/uesave-rs @ 1917a22ab69e9a4045e613d9d7f39a49fe00bd46 · license: MIT
    Rust library and CLI that reads and writes Unreal Engine GVAS save files to JSON; Header::read in uesave/src/lib.rs is the reference for the header and property tags.
    Tested on: source read, not run: source read, not run · checked 2026-10-18; last activity 2026-04-23; Note: the latest release ships binaries; the wiki links only the source, never the binaries

Pitfalls

  • Struct values of well-known types (Vector, Rotator, Quat, Guid, DateTime, LinearColor) have a fixed binary form; uesave treats engine 5 as large-world-coordinates (doubles).
  • Unknown or game-specific struct types can only be skipped with the size field; keep size consistent when editing.
  • Unverified: some games compress or encrypt the whole file, in which case the first bytes are not GVAS. Identify the wrapper first (Technique:Reverse engineering game save files).

See also Library:Unreal Engine.