Param.json
PSP/PS3/PS4/Vita used a param.sfo file for metadata. PS5 games have a similar file, but instead of .sfo it is now .json.
There are three types of param.json: param.json, origin-param.json and target-param.json. What the differences are and what they are for is currently unknown.
addcont
serviceIdForSharing
Format: List <String>
Required: Yes?
ageLevel
Format: Dictionary <string, int>
Required: Yes?
Agelevel contains a dict of age levels for different regions. Aside from the default age level, the following regions are available:
- AE
- AR
- AT
- AU
- BE
- BG
- BH
- BO
- BR
- CA
- CH
- CL
- CN
- CO
- CR
- CY
- CZ
- DE
- DK
- EC
- ES
- FI
- FR
- GB
- GR
- GT
- HK
- HN
- HR
- HU
- ID
- IE
- IL
- IN
- IS
- IT
- JP
- KR
- KW
- LB
- LU
- MT
- MX
- MY
- NI
- NL
- NO
- NZ
- OM
- PA
- PE
- PL
- PT
- PY
- QA
- RO
- RU
- SA
- SE
- SG
- SI
- SK
- SV
- TH
- TR
- TW
- UA
- US
- UY
- ZA
applicationCategoryType
Format: Int
Required: ?
Possible values: 0
applicationDrmType
Format: String
Required: ?
Possible values: Upgradeable standard
asa
Required: No
code
sign
Format: List <String>
Required: ?
attribute
Format: Int
Required: ?
attribute2
Format: Int
Required: ?
attribute3
Format: Int
Required: ?
conceptId
Format: String
Required: ?
A concept id is an over-arching id for a game or entity. A game can have multiple different content-ids for different regions, but they will all have the same concept id.
contentBadgeType
Format: Int
Required: ?
Possible values: 1
contentId
Format: String
Required: Yes
contentVersion
Format: String
Required: ?
Example: 01.000.000
downloadDataSize
Format: Int
Required: ?
gameIntent
permittedIntents
Format: List <Dict <"intentType", String>>
Required: ?
Possible values for intentType: launchActivity
kernel
Required: No
cpuPageTableSize
Format: Int
Required: No
flexibleMemorySize
Format: Int
Required: No
gpuPageTableSize
Format: Int
Required: No
localizedParameters
Contains a dictionary of localized titles. As with ageLevel there is a default entry called defaultLanguage. The defaultLanguage entry does not have the same contents as the example entry below, but contains a simple string with the language code of the default language (e.g. en-US).
Example of localized entry:
"<language-identifer>": {
"titleName": "Title of your game"
}
Where <language-identifer> is one of the following:
- ar-AE
- cs-CZ
- da-DK
- de-DE
- el-GR
- en-GB
- en-US
- es-419
- es-ES
- fi-FI
- fr-CA
- fr-FR
- hu-HU
- id-ID
- it-IT
- ja-JP
- ko-KR
- nl-NL
- no-NO
- pl-PL
- pt-BR
- pt-PT
- ro-RO
- ru-RU
- sv-SE
- th-TH
- tr-TR
- vi-VN
- zh-Hans
- zh-Hant
masterVersion
Format: String
Required: ?
Example: 01.00
pubtools
Required: ?
creationDate
Format: String/Date (yyyy-mm-dd hh:mm:ss)
Required: ?
loudnessSnd0
Format: Float as String
Required: No
submission
Format: Bool
Required: ?
toolVersion
Format: String
Required: ?
Example: 1.00
requiredSystemSoftwareVersion
Format: String/Hex
Required: ?
Example: 0x0114000000000000
sdkVersion
Format: String/Hex
Required: ?
Example: 0x0100000000000000
titleId
Format: String
Required: ?
Example: ABCD12345
userDefinedParam1
Format: Int
Required: ?
userDefinedParam2
Format: Int
Required: ?
userDefinedParam3
Format: Int
Required: ?
userDefinedParam4
Format: Int
Required: ?
versionFileUri
Format: String
Required: Yes?