Ready to Run vs Files Needed
PortMaster games and handheld Linux guide · Updated October 2026
Ready to Run usually means a PortMaster package can start without adding proprietary game assets. Files Needed means you must place specified files from a legitimate copy of a game into the port folder.
Why the distinction exists
Many ports use an open-source engine or launcher but cannot redistribute copyrighted graphics, audio or level data. In those cases, PortMaster can distribute supporting code and scripts while the player provides original files.
Recognizing a ready-to-run entry
A ready-to-run port can still have restrictions. It may require a compatible runtime, enough storage and a supported CPU architecture. The label is not a promise that the title runs equally well on every handheld.
Recognizing a files-needed entry
Read the entry instructions to find the correct names, versions and case-sensitive directories for game assets. Some ports expect a specific release or data archive rather than any similarly named copy of a game.
Avoid incorrect file placement
A common mistake is creating an extra nested folder while unzipping. Compare the expected path with the actual SD-card layout. On Linux, mixed upper- and lower-case filenames are often different, even when they look equivalent on Windows.
Verify and document the working setup
After a port launches, note the game version and storage location. Back up saves separately from game assets. On future updates, check the port changelog before replacing files or assuming old data remains compatible.
Common questions
Are all ready-to-run games free?
The label describes the file requirements of a port entry, not a general statement about licensing or price.
Can PortMaster download commercial game files for me?
Do not assume so. Files Needed entries typically expect users to provide their own legally obtained game data.
Next steps and references
The right setup depends on your firmware and the individual game port. Verify the current compatibility notes before copying files, changing permissions or replacing runtimes.