FRF vs SGO: Understanding VAG Flash Container Formats

Anyone who works on Volkswagen group cars meets two file types sooner or later: FRF and SGO. Both carry control unit software, both are written over OBD, and both appear in our FRF/SGO catalogue. They are not interchangeable, though, and picking the wrong one wastes time. Here is what each format is and when to use it.

SGO: the engineering format

SGO is the older container used by VAG engineering and production tools. It is essentially a ZIP archive holding the flash data blocks and a small description file that tells the flasher which memory areas to erase and write. Because it is not encrypted, many third-party tools can open it, extract the calibration for tuning work, or repack it. VCP, ODIS-E and several bench tools accept SGO directly.

FRF: the dealer format

FRF is the encrypted successor introduced with ODIS. Inside it is the same kind of data as an SGO, wrapped in an encryption layer that only the official flashing routine can open. Dealers receive updates as FRF; the file name usually contains the part number and the software version (for example FL_04L906021N_7636.frf). ODIS-E and VCP handle FRF natively; most aftermarket tuning tools cannot read the contents without converting it first.

Side by side

	SGO	FRF
Encryption	None	Yes
Typical source	Engineering / older ODIS versions	Current dealer distribution
Tools that flash it	ODIS-E, VCP, some bench tools	ODIS, ODIS-E, VCP
Usable for extracting calibration	Yes, directly	After decryption/conversion
Availability for new modules	Rare after ~2015	Standard

Reading the part number and version

Every container is valid for one control unit part number and hardware index. Our product titles follow the pattern “part number + version + FRF/SGO”, for example “3Q0959655A 0189 FRF FILE” for an airbag module or “1K0907115N 0020 SGO FILE” for an engine ECU. The first three characters of a VAG part number identify the platform, the middle group the module type (906/907 engine, 927 gearbox, 959 comfort and airbag, 937 body control, 920 cluster), and the suffix letters the revision. Compare it with the number the diagnostic tool reports before flashing.

When a container is not enough

Containers are written through the module’s own bootloader over CAN. A module that no longer communicates, or one whose bootloader was damaged by an interrupted flash, cannot accept a container. In that case you need the raw original dump and a bench or boot-mode tool such as PCM Flash, KTAG or FLEX. Our recovery guide covers that path.

Which one should I buy?

• Updating or downgrading a working module with ODIS-E or VCP: FRF (or SGO if that is what is available for the version).
• Extracting the stock calibration for tuning: SGO if listed, otherwise the raw dump.
• Reviving a dead module: raw original dump, not a container.

Read the flashing steps in our FRF flashing guide, and if the version you need is not in the shop, send the part number through the file request form.