What is the SFO file format?
A .sfo file - always named param.sfo inside a game package - is a compact binary metadata container used across Sony PlayStation platforms from the PSP through PS5. It stores the key-value parameters that the console dashboard (the XMB on PS3 and PSP, the home screen on PS4 and PS5) reads to display a game's title, title ID, version string, required system software version, and parental control rating.
The format uses a fixed 16-byte binary header beginning with the magic bytes \x00PSF, followed by a key string table of null-terminated UTF-8 keys and a data table of typed values. Values may be UTF-8 strings, 32-bit integers, or raw byte arrays. Common keys include TITLE, TITLE_ID, APP_VER, PARENTAL_LEVEL, and SYSTEM_VER. The file is little-endian and carries no encryption or checksum; integrity is managed at the parent .pkg container level.
param.sfo is never distributed as a standalone file. Users encounter it when extracting a PSP, PS3, PS4, or PS5 game package, backup, or update archive. The file is typically under 2 KB. Tools such as PS4 SFO Reader/Editor (hippie68) allow reading and editing these parameters - useful for homebrew development or regional title patching. The PSP/PS3/PS Vita variant uses header version bytes 01 01; the PS4 introduced an updated variant with additional keys.
Security & safety
RISK: LOWPARAM.SFO files are passive metadata and cannot execute code. The risk is context-specific: modifying a param.sfo in a game package to lower the required firmware version is a common CFW/homebrew technique; the legal and console-ban implications depend on the user's situation. Downloading random .sfo files from the internet carries the usual software risk.
Format details
in a nutshell- CuteFTP Site File Object (ServerFTP connection file) - CuteFTP used .sfo for saved FTP server connection profiles; format is proprietary GlobalSCAPE binary.
- Bitstream Font Outline File - Legacy Bitstream font technology used .sfo as a font data sidecar; effectively obsolete, no modern software uses it.
Programs that open SFO files
Windows4 apps
PS4 SFO Reader/Editor (hippie68)
Free Open the tool, drag param.sfo onto it or use File > Open to browse to the file; fields are displayed and editable.
PS3Tools / PARAM.SFO Editor
Open-source Run PARAM.SFO Editor from the PS3Tools suite, open the .sfo file to read and edit PS3 metadata fields.
SFO Extract (legroom.net)
Free Command-line tool: sfo-extract param.sfo - outputs all key/value pairs as text.
CuteFTP (for CuteFTP .sfo only)
Paid CuteFTP reads its own .sfo site files (FTP connection profiles) - unrelated to PlayStation PARAM.SFO. Technical details
deep spec| Magic bytes | `\x00PSF` (0x00 0x50 0x53 0x46) at offset 0 |
| Byte order | Little-endian |
| Container | Custom Sony binary with fixed header, key string table, data table, and index table |
| Header size | 16 bytes fixed; stores offsets to key table and data table, plus total entry count |
| Format version | Bytes 4-5: `01 01` (v1.1) for PSP, PS3, and PS Vita; PS4/PS5 use an updated variant |
| Value types | UTF-8 strings, 32-bit unsigned integers, and raw byte arrays |
| Key examples | `TITLE`, `TITLE_ID`, `APP_VER`, `PARENTAL_LEVEL`, `SYSTEM_VER` |
| Data security | No encryption or checksum within the SFO; integrity is delegated to the parent PKG container signing |
| Typical file size | Under 10 KB; PS3 `PARAM.SFO` typically 500 B - 2 KB |
| Platforms | PSP, PS3, PS Vita, PS4, PS5 |
| File naming | Always `param.sfo` (lowercase) inside game packages; never distributed as a standalone file |
| Data storage | Values stored as raw uncompressed bytes - UTF-8 strings or 4-byte little-endian integers in flat tables |
| Released | ~2005 (PSP, PlayStation Portable) |
| Latest version | PS4/PS5 variant (updated ~2013 with PS4 launch) |
| Specification | www.psdevwiki.com |
SFO conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about SFO files.
