DEVELOPER TOOL

Application JSON Generator

Create a PS Vita Alive Store apps/*.json file using a guided form. The generator validates the current catalog rules, loads official categories/authors, checks duplicate Title IDs, and never edits the catalog directly.

Create mode: the app ID and Title ID must be new in the catalog.
Loading PS Vita Alive Store categories, authors and catalog...

1. Identity

Basic identity of the homebrew entry. In Create mode the Internal ID is generated from the name and cannot be edited.

Display name shown in the store and website. Use the official title when possible.
Auto-filled from the name in Create mode (e.g. my-cool-app → file my-cool-app.json). Only lowercase, numbers, hyphens and underscores.
PS Vita TITLE_ID from param.sfo (9 characters, e.g. VITASHELL). Must be unique in the catalog.
Short text for lists and cards. Keep it clear and under ~200 characters when possible.
Full description for the detail page. You can use several paragraphs; line breaks are kept.

2. Authors & category

Search authors by name or ID, select as many individual profiles as needed, or create a new author reference. Subcategories are restricted to the selected official category.

Type a name or ID to filter the official author list. Selected authors appear as chips and can be removed individually.

Click to add or remove. No Ctrl needed. Only subcategories of the selected category are shown.

3. Release

Release information used by the catalog and update logic.

Version string of this release (e.g. 1.2.0 or v3), matching the download when possible.
Release date of this version (YYYY-MM-DD).
What the user needs: firmware, plugins (NoNpDrm, etc.), storage, or “None”. Line breaks are allowed.
Pick a unit (B / KB / MB / GB). The JSON will store the size in bytes automatically.
Verified = works as expected · Legacy = old but kept · Archive = historical only.

4. Media

Public direct image URLs only (must open the image itself, not an HTML page). Preferred: PNG. Good hosts: GitHub raw, Archive.org, Imgur direct links.

Optional. Direct link to the app icon (ideally icon0.png, ~128×128). Leave empty to use the category fallback. Do not use GitHub “blob” page links — use raw.githubusercontent.com or Archive.org file URLs.
Optional, 1–5 images. Each field must be a direct image URL (PNG/JPG). Prefer Vita resolution (~960×544). Same rule: no HTML gallery pages.

5. Links

Download and reference links. Drag ⋮⋮ to reorder. Mark one link as Recommended (main install button).

Link types
  • Download — main .vpk (or similar) install package.
  • Data Files / Game Files — extra .zip data extracted on the Vita. Set extract_path (usually ux0:data/).
  • Mod / Mod Pack / Patch — mods or patches; also use extract_path when they are zips.
  • PKG / DLC / Update — package content (games catalogs / updates).
  • Mirror / Repository / Official Website / Documentation / Issues / Community / Other — informational links (not installed by the client as the main payload).

Size: optional per link; pick B/KB/MB/GB — JSON stores bytes. URLs: must be public http:// or https:// direct file links when possible (GitHub Releases, Archive.org, MediaFire, etc.).

6. Optional metadata
Human-readable page for this version (GitHub Releases, blog post, etc.).
Project homepage or source repository.
Short label for the source (e.g. GitHub, GitLab).
Optional external ID if you track one.
What changed in this version.
Optional counter; leave empty if unknown.
Legacy optional field (bytes). Prefer size on Data/Game Files links instead.
Legacy optional field. Prefer a Data Files link in section 5.
Optional rating; leave empty if unused.
Optional last-updated timestamp.