Your sources.
Your console.

What has been tested

The current build has worked well in a small group after several rounds of fixes. Host builds and local regression checks have passed. More consoles may still expose launch, extraction or installation failures. Treat this as a public test and report what happens on your setup.

Background downloads

Shell-resident operation depends on compatible GoldHEN process/plugin capabilities and the matching worker. If those are unavailable, keep SSPI open for the in-app paths. A firmware compatibility matrix has not yet been established.

1. 01

   Install the beta package

   Install sspi5.11.1.pkg over the existing SSPI application. Launch once to stage the updated resident, fully restart the PS4, re-enable GoldHEN and reopen SSPI. Check for BETA 5.11 / 8629117696fb in the footer. Closing SSPI alone leaves the previous resident loaded.

2. 02

   Connect a download service

   Press OPTIONS and open Settings → Connections. Scan the QR with a phone on the same LAN. Save your service keys, enable the services you want to use and choose your preference.

3. 03

   Check your source

   Open Package sources and confirm your chosen source is enabled. Other compatible .gssource packages can be added through the phone setup page.

4. 04

   Search and choose

   Return to Search. Press × on the search field to enter a name or CUSA ID. Open the title and use L2 to cycle available regions/source variants. Inspect package types, versions and mirrors before queuing.

5. 05

   Follow the individual files

   Switch to Downloads. Press R2 on the selected game to open the drawer. Left/right switches Packages, Files and Errors; up/down selects or scrolls. Press L2 to close. A full download bar is not proof of installation; wait for the installation result and confirm the content on the PS4.

The QR opens SSPI's setup page on your console. Use the address shown by your PS4; it includes the current local IP and a pairing token. This documentation website is not the setup server.

Save a service

In Link services, paste your own keys and choose your enabled and preferred download services. Save before leaving the page. Several service keys can remain stored. A saved key does not confirm that a subscription is active or that a particular host is supported.

Switch services

In Settings → Connections, manage Real-Debrid, TorBox, AllDebrid or Premiumize. Switching preserves the other saved keys and applies to new downloads; it does not move a running transfer between services. The Downloads touchpad menu also accepts direct package/archive links.

If the page does not open

Keep SSPI open, rescan the current QR and check that the phone can reach the console. Guest-network isolation, a phone VPN or an old console IP can prevent access. Ethernet and Wi-Fi can be used together on the same reachable LAN.

A .gssource is a source connector packaged as a ZIP. It describes where and how SSPI searches and resolves package information. It is not a game, a PKG or a service account.

Bundled sources

Source descriptors tell SSPI how to search and resolve package information through its engine. Sources can use static catalogs or configured APIs. A successful source installation confirms that the connector was accepted; it does not guarantee that every catalog entry or host is currently available.

Add or enable a source

Open Connections → Package sources. Highlight a source and use the displayed action to enable or disable it. To add another, open the phone setup page and supply the actual .gssource download URL. A GitHub file-view page or website landing page is not the archive itself.

Updates and removal

Source upgrades can repair result mapping without replacing the application. The current installer preserves an existing usable source if an upgrade fails. Disabling or removing a bundled source is remembered. Sources supplied separately should be intended for PS4 and the supported engine version.

What the engine reads

The manifest identifies the source, version and engine. Recipe sources describe requests and result mapping; remote-API sources call a configured result service. SSPI validates the package layout and declared files. Valid metadata does not establish publisher trust or package compatibility.

See the source models and source package reader for the implementation.

Search by title or CUSA ID. Opening a result resolves its available packages. Search and package resolution are separate steps, so a title may appear even when one of its download routes is unavailable.

One title, available regions

Matching titles are grouped while retaining their region, title ID and source identity. Press L2 in details to cycle the available variants. The compact region hint shows the current choice and position. Review the title ID before queuing an update or DLC.

Read the package information

Use the type tabs for All, Base, Updates, DLC and Backport. The selected package shows available version, size, required firmware, source and mirror information. Missing values remain unknown. A firmware number is not an application version.

Mirrors are alternatives

All source-provided hosts are visible. A listed host may still be unsupported by your selected service. Pick a usable mirror for the package you want; do not queue every mirror as a different update.

Recommended packages

Recommendations depend on the source's metadata. Review the CUSA, region, package kind and update/backport choice before proceeding. An exact-region result is not silently replaced with another region.

Downloads are grouped by game. The selected game expands to show artwork and progress; other games remain compact. Press R2 to open the inline drawer beneath the selected game. Its rounded outline shows the job state without a separate transfer circle.

Use the file drawer

Left/right switches between Packages, Files and Errors; up/down selects or scrolls. Select a package on Packages, then switch to Files to inspect its incoming volumes and extracted packages. Completed extracted packages receive individual installation checkmarks. Controls stay inside the drawer until L2 closes it.

A failed game opens on Errors, with scrollable messages and an attention strip on the other tabs. With the drawer closed, L2 cycles All, Active and Attention; the touchpad opens direct links, debrid files and USB imports.

Pause, cancel or retry

Focus the relevant game or package and follow the centered action row. The actions change with its state. Canceling a task, removing queue history and deleting downloaded storage are different operations.

Square outside the drawer requests removal of all queued packages for that game in one confirmation. Inside the drawer it targets the selected package. Active writers must stop before downloaded files are removed. Installed games and original USB files are kept; an unconfirmed installation may require attention before removal can finish.

Completion and stale status

The latest beta includes installed-content checks to reconcile stale BGFT counters and false stalls. A full transfer bar alone is still not installation proof. If the PS4 confirms completion while SSPI remains Installing or Failed, capture both states and the build ID before retrying.

A remaining patch integrity-verification failure path can leave the resident status at Installing. Report the exact system error and package combination rather than repeatedly starting duplicate tasks.

Choose deliberately

1. Check the installed title ID, region and base version.
2. Choose an update or backport intended for that base and firmware.
3. Let the base finish before dependent packages. Close the game being updated.
4. Confirm the version in the PS4 interface and test launch after installation.

A shared CUSA ID and structurally valid file do not prove that every base/patch combination is compatible. Do not queue all update revisions, mirrors and backport variants as consecutive steps.

Library update checks

Checks use enabled sources and cached metadata. A newly published update can take time to appear. Missing version information or a source failure is not proof that a title is up to date.

When BGFT reports an error

Keep the exact hexadecimal code and the corresponding PS4 Notifications details. Record whether the error occurred before installation, during transfer, or after the system reported completion. Preserve recoverable package files until the task's ownership is resolved.

SSPI checks file headers to distinguish a direct PKG from an archive, even when source metadata describes it incorrectly. Direct PKGs skip extraction. Supported RAR, multipart RAR, ZIP and 7z files are staged and their installable packages extracted. Incoming filenames in the drawer reflect the detected format.

Passwords and progress

Settings → General → Retry source passwords is enabled by default. When a password is rejected, SSPI can try up to four passwords supplied by the source, preserving exact spelling and brackets. This does not repair missing volumes or corrupted files. Save changes after changing the setting.

RAR progress uses the total expanded package size read from archive headers. The app shows header reading while that total is unknown, then reports extracted bytes and percentage. Extraction is a separate stage from downloading and installation; its speed and remaining time depend on decompression and storage.

Multipart sets

Every required part must belong to the same archive set and finish downloading. A .part1.rar or numbered volume is not a standalone package. Missing, truncated or mismatched parts can prevent extraction even when the first volume is complete.

Plan for peak storage

Large or solid archives take time on the PS4's HDD. Network bandwidth settings do not accelerate decompression. Unsupported archive features or a damaged upload may require a different mirror or a corrected set.

Keep useful retry files

Failed installations can retain complete files. Do not manually delete staging data while a worker or system task may own it. Use the queue and Storage controls after work has finished or cancellation has been confirmed.

Open Settings → Storage to inspect downloaded files and eligible leftovers. This is not a browser for the entire PS4 drive and does not uninstall installed titles.

Delete through the app

Refresh the listing, select the file and follow the displayed delete and confirmation actions. Check its name and size first. Cleanup protects active work and recovery information; a file that appears unused can still belong to a pending install.

History and storage differ

General → Clear removable history clears eligible queue entries. It does not mean that every downloaded file has been removed. Use PS4 system storage management to uninstall installed content.

Deletion is refused

Finish or cancel relevant pending/background jobs, wait for confirmation and refresh. If ownership cannot be confirmed, retain the files and report the task state. Do not delete journals or reset queue files to force an installation past an error.

Accent and background

Settings → Appearance provides accent choices and built-in backgrounds. The phone setup page can also save appearance settings. Restore original charcoal to return to the plain background while keeping the chosen accent.

For the new look, open Settings with OPTIONS, switch to Appearance with L1/R1, select Pink in the accent grid and press Cross. Select the Background row and use left/right to choose ASCII Flowers. Appearance changes save automatically. Flowers use your accent color and a cached static pattern; Reduce Motion also disables the Downloads outline pulse.

Built-in patterns provide the available background options. Arbitrary uploaded background images are not part of this beta's setup flow.

Quiet interface audio

Settings → Sound has separate switches for background music and interface sounds, plus volume. The default is 35%, with music mixed below the effects. Left/right changes volume in 5% steps; zero mutes it. Preferences save automatically.

Navigation and completion cues are designed to stay subtle. Audio runs away from the rendering thread and is optional; failure to open an audio device should leave the application usable without sound.

1. 01

   Search

   Enabled sources return title records for your query. The app combines those results and keeps their source identity.

2. 02

   Resolve

   Opening a title produces package candidates: kind, title ID, version, region, host, link and any supplied size, firmware, archive or checksum information.

3. 03

   Unlock

   An enabled service account requests a usable download route. A source returning a host link is not the same as the provider accepting it.

4. 04

   Transfer

   The application or resident worker transfers the data, preserves progress and applies the configured bandwidth limit. The transfer path coalesces small reads with bounded buffers.

5. 05

   Prepare

   Archive sets are extracted and package structure, length and available identity/integrity information are checked. Missing expected metadata limits what can be verified.

6. 06

   Install

   BGFT and the package-specific installation paths register work, track progress and reconcile installed content. A task being accepted does not mean it has finished.

Caching

Search results, resolution data, eligible responses and artwork are cached to avoid repeating work. Source changes, expired links and provider failures can still need fresh requests. Caching does not guarantee that an old mirror remains available.

The bundled connector uses JSON results. The codebase also retains compatibility engines for other source formats. Read the source layout to find the managed and native implementations.

Mbps and MB/s

Connection plans usually advertise Mbps; the download display uses MB/s. Divide by eight for the theoretical decimal equivalent, before protocol overhead, disk work and host limits.

Bandwidth limit

Open Settings → General → Bandwidth limit. Use Unlimited when measuring the fastest available route. The old Parallel ranges setting is no longer the user-facing transfer control.

A 300 Mbps connection has a theoretical ceiling of 37.5 MB/s before overhead. SSPI cannot promise 30 MB/s for every host, provider route, console or disk. A steady 11 MB/s is also consistent with a 100 Mbps link, but that must be checked at the router or switch rather than assumed from the number alone.

Compare one route at a time

Use Ethernet, the same large file, host and debrid service, with other disk/network work quiet. Record sustained speed after startup and the bandwidth setting. A console internet test is not a measurement of that specific download route.

TorBox preparation and rate limits

An uncached file may need to reach TorBox before it can be delivered to the PS4. That wait is provider preparation, not console transfer speed. Unsupported hosts and account limits can still stop resolution. If a provider returns HTTP 429, wait for its retry window.

Open the Downloads drawer with R2, select Errors and keep the exact error wording. Search, service unlocking, extraction and installation are different stages.

OPTIONS opens or closes Settings. L1/R1 switch main tabs or settings pages. Follow the bottom action row for the current screen.

Data stays on the console

Runtime data remains under /data/GameSearch/, preserving the app's historical directory identity. Settings, credentials, sources, queue state, staging data and caches belong to that local workspace. Updating the same application does not require publishing or sharing these files.

Development source

The GitHub repository contains selected production source, manifests, notices and this public guide. SDKs, runtime dependencies, source descriptors and build outputs remain separate. A source ZIP is not an installable package or a complete build environment.

See the build requirements, license and third-party notices. Build artifacts belong under the development workspace's Build-Output directory.

5.11.1 remains a public beta. The managed/native build, package verification and focused regression checks passed. Console screenshots confirm the updated region controls, drawer and appearance options on build 8629117696fb. More hardware and package combinations may still expose freezes, extraction problems and installation errors.

The guide was updated on 15 September 2026 for the public beta. Read the release notes for the package download and checksum. Local build/test results do not establish universal firmware support, a fixed frame rate or a guaranteed download speed.

SSPI version and footer build ID:
PS4 model / firmware / GoldHEN version:
Worker status (if using background downloads):
Connection: Ethernet or Wi-Fi
Service / host (no keys):
Source name and version:
Title ID / installed base version:
Update, backport or DLC version:
Package type: direct PKG or archive set
File size / free storage / bandwidth limit:
Steps to reproduce:
Stage that failed / full SSPI error:
PS4 system status and error code:
Expected result / actual result:

Remove keys, pairing tokens, signed URLs and private settings from screenshots and logs. When SSPI and the PS4 disagree, include both states. Reports that reproduce an issue help more than a summary saying it does not work.