DirectPackageInstaller: pushing PKG files to a PS4 or PS5 from your desktop

Three ways to reach the console, all of them homebrew

The readme opens by stating what the tool is: a tool to preview and send PKG files to your PS4 or PS5 using direct download links.

What makes it non trivial is the delivery mechanism, and there are three of them.

Remote Package Installer Homebrew. GoldHEN Payload Server. And the etaHEN DPIv2 API.

Every one of those lives on the console side, and every one of them requires a console that is running homebrew software. That is the single most important fact about this project, and it belongs in the first paragraph of any evaluation. On a stock console there is no payload server to talk to, so the tool has nothing to connect to.

The tool itself is a plain C# .NET application, and the repository shows the pieces: a DirectPackageInstaller.sln solution, a DirectPackageInstaller/ directory for the application, a Payload/ directory, a DHCPServer directory, an HttpServerLite directory, LibOrbisPkg for the package manipulation, and a Files/ directory. The DHCPServer component is there to give the console a network address over a LAN cable, which pairs with the auto LAN cable connection feature listed for Windows.

So the flow is: your desktop fetches the package, and the tool talks to a payload server running on the console to tell it to download and install it. The console does the final install, the desktop does the fetching and the orchestration.

The four download modes and what each one needs

The readme documents four modes, and the differences between them are operational rather than cosmetic.

Direct Download Mode is the baseline. Launch Remote Package Installer or enable GoldHEN Payload Server, open DirectPackageInstaller, paste a direct PKG URL into the PKG URL field, click Load and wait, click Install and wait again. The readme notes that once it is done you can close the application or shut down your PC, which tells you the console completes the work on its own.

Proxied Download Mode is for PS4s without internet access. You enable it under Options and Proxy Downloads. The tool's automatic proxy server fetches the file on the PC's behalf and passes it to the console, which is the only way to install anything on a console that cannot reach the network itself.

Segmented Download Mode is described as the fastest. You need enough free disk space, enable it under Options and Segmented Downloads, and the package is downloaded and preloaded before installation. The readme carries a caution: in segmented mode the PS4 cannot track download progress accurately, so the console's own progress display is not to be trusted.

Compressed File Mode is always proxied. You paste the direct URL of a compressed file rather than a PKG, wait for Load, optionally pick a specific PKG from the file list, and then Install. RAR and 7z archives are supported, and the readme notes that resumable downloads work only for uncompressed files, which is a useful thing to know before you start a large transfer that drops halfway.

Beyond the modes there is support for PSN update manifests, which is how split PKG downloads are handled, and support for installing PKGs from an NFS source, which is covered separately below.

Hosting services, and the one with a wait timer

The supported file hosting list is longer than a simple direct link, and it dictates what you can paste into the URL field.

Any direct link without authentication is supported, which covers most of the web. Then there are the premium link resolvers that need an API key: AllDebrid, RealDebrid and DebridLink each link to their own API key page. The readme is explicit that a key is required for those three.

Then there are the ordinary file hosts: Google Drive, Mediafire and PixelDrain. And 1Fichier, with a condition that is easy to miss: you must wait 60 minutes after each download. That is a free tier behaviour of the service rather than a limitation of the tool, but it means a 1Fichier source is a poor choice when you want the file now.

There are two more features in the list worth calling out. There is a Command Line Interface, so the whole flow can be scripted rather than driven through a window. And there is JDownloader Click'n Load support, which means the tool can act as a target for JDownloader's one click loading, which is how people usually feed a captured download link into it.

The readme also mentions an automatic proxy server to accelerate downloads, and explains the reason in a sentence that the documentation truncates: since the PS4 has much better speeds over the proxy than it would fetching the file itself, the PC becomes the fast network path. That is the whole justification for the proxy mode, and it is why the proxy is automatic rather than optional in the compressed and offline cases.

Building an NFS source, and a Windows caveat

The NFS section is a short addition that lets you point the tool at a file server rather than a web host, and it has two URL formats with different behaviour.

The first is nfs://YOUR_NFS_IP_OR_HOSTNAME/ExportedPath/FilePath/FileName.pkg, where the path starts with the exact exported directory as configured in the NFS server's /etc/exports. DPI mounts that specific export and looks for the file within it.

The second is nfs://YOUR_NFS_IP_OR_HOSTNAME/FilePath/FileName.pkg, with no export path given. In that case DPI attempts to search across all available exports on the server to locate the file, and the readme notes that this may slow down the initial access if the server has many exports.

That difference is the practical detail. Naming the export makes the mount deterministic and fast; omitting it makes the tool convenient at the cost of enumerating every export on the server.

There is also a Windows caveat. The readme says DPI is incompatible with winnfsd because of a specific bug, issue 88 in the winnfsd tracker, and suggests haneWIN NFS Server as the Windows alternative. So the NFS source path is usable on Unix hosts and needs a different server implementation on Windows.

The macOS command line usage is worth noting too, since the macOS builds are the only ones that are self contained. You run the app directly with ./DirectPackageInstaller.Desktop, and in some cases you need dotnet DirectPackageInstaller.Desktop.dll instead.

Building it on Windows, and the Gatekeeper dance on macOS

The install instructions are for end users rather than builders, and the download matrix is wide.

There are Windows builds for ARM, ARM64, x64 and x86. Android builds for the same four architectures. Linux builds for ARM, ARM64 and x64. And macOS builds for ARM64 and x64, in two flavours: CLI builds and App builds, and the App builds come as a zip and as a DMG for drag to Applications.

The runtime requirement differs by platform. On Windows, Linux and Android you need to install the .NET 8 Runtime first. macOS builds are self contained and do not require a separate .NET install.

That self containment has a consequence on macOS, and the readme explains it. The App is ad-hoc signed so it launches on Apple Silicon without further steps, and if Gatekeeper still blocks it after extracting the zip, you remove the quarantine attribute.

xattr -dr com.apple.quarantine /Applications/DirectPackageInstaller.app

For someone building from source rather than downloading a build, the repository holds a Visual Studio solution, a Build.cmd, a global.json and a compile.txt, along with the DHCPServer, HttpServerLite, LibOrbisPkg and Payload subprojects. The solution file is DirectPackageInstaller.sln and the .DotSettings file beside it carries the shared IDE configuration.

The release history shows the maintenance pace. The listed versions are 8.3.3 with support for DebridLink and bug fixes from 2025-10-26, 8.3.2 fixing RealDebrid from 2025-10-18, and 8.3.1 adding initial NFS support from 2025-05-25. The last push was on 2026-06-28.

The licence is GPL-3.0, which is worth pausing on for a Windows tool with a commercial feel. The readme and the repository carry the GPL terms, and for anyone who wants to modify and redistribute this, or embed it in something else, that is a copyleft obligation that needs proper advice rather than a summary.

Where DirectPackageInstaller is the wrong tool

There are three clear reasons not to reach for this.

The first is the hardware requirement, and it is absolute. All three delivery methods are homebrew components on the console, so on a stock PS4 or PS5 the tool does nothing. If you are not already running Remote Package Installer or GoldHEN, the first task is not to install packages but to get that side working, and that is a separate project with its own constraints and its own risk of a console that no longer boots.

The second is that the tool does not obtain packages. It takes a URL you supply and orchestrates a download. Everything about what you install, whether it is a homebrew app, a licensed game backup, or something else, is entirely outside its scope and outside its knowledge. The supported hosting list includes Google Drive, Mediafire and the premium link resolvers, and the readme does not restrict what kind of PKG you point it at. That is a deliberate neutrality in the tool and it is also the thing to think about before you use it.

The third is the operational friction of the modes themselves. Proxied mode is mandatory for a console without internet access, which means the download is bound to your PC staying switched on. Segmented mode is the fastest but needs free disk space on the host and gives you an unreliable progress display on the console. Compressed mode is always proxied, and resumable downloads work only for uncompressed files, so a dropped connection on a large archive means starting over. And the 1Fichier support carries a mandatory 60 minute wait, which rules it out for anything urgent.

On the alternative, the difference in approach is where the fetching happens. The traditional method is to download the PKG in a browser and hand it to the console over a local network share or a USB drive, which needs no homebrew payload server on the console for the transfer itself and gives you full control of the file. This tool inverts that: the console pulls the package itself over HTTP, which is why it can support PSN update manifests and split packages that a manual transfer makes awkward, and why it can install without the console being able to reach the internet.

For a console on a fast network with a browser, the manual route is simpler and needs no extra software on the console at all. For a console with no internet access, or for split update packages, this tool does something the manual route cannot, which is the real argument for it.

Editorial conclusion

DirectPackageInstaller suits a console owner who already runs Remote Package Installer or GoldHEN and wants to install a package from a direct link without a browser session, and it does not suit a stock console, since none of the three delivery methods exist on unmodified hardware. Before you use it, confirm your console has a working Remote Package Installer or GoldHEN payload server, and decide which download mode fits your setup, because the proxy mode is required for a console with no internet access and the segmented mode needs free disk space on the host.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. marcussacana/DirectPackageInstaller on GitHub
4. README
5. Releases