Start with the right layout.

1. Prepare your input

The relinker expects a clean ELF executable. Keep its bundled ELF modules beside it in sce_module/, sce_modules/, or prx/. The first two cannot coexist; prx/ may accompany either. Having none of these directories is also an error in the current documentation.

source/
  input.elf
  sce_module/
    <bundled ELF modules>

Use an input you are legally entitled to use. The project and this guide do not supply title files or instructions for obtaining protected content.

2. Choose Windows output

In PowerShell, if the relinker has been saved as relinker.exe in the current directory, the basic conversion is:

& '.\relinker.exe' --windows 'source/input.elf' 'app.exe'

--windows is essential. Naming the output app.exe without that flag still selects Linux ELF. For an Intel host, add --to-intel to translate supported AMD-only instructions in the executable and bundled modules.

The optional --windows-diagnostics switch adds startup dependency diagnostics and requires --windows. --windows-gui selects the GUI subsystem; a console output is more useful while collecting errors.

3. Choose Linux output

The documented default output is Linux ELF. With the relinker available in the current directory:

./relinker 'source/input.elf' 'app.elf'

Add --to-intel for an Intel host. This option translates supported instructions; unsupported instructions or unreachable conversion stubs can still stop the conversion.

4. Assemble the runtime

app.exe  (Windows) or app.elf  (Linux)
libs/
  <AnyPS5 system libraries for the target OS>
app0/
  <application resources>
  sce_module/
    <converted bundled modules>

Use the exact generated locations printed after Guest module:. The relinker preserves the input directory name under app0/; your title may therefore use sce_modules/ or prx/ instead.

Copy or extract the AnyPS5 system libraries into libs/. Place the application's resources into app0/ separately. Original title modules are not AnyPS5 system libraries and do not belong in libs/.

5. Read the result before launching

Exit code 0 means the conversion succeeded. Code 1 signals invalid arguments; code 2 signals a conversion failure with an error on stderr. A successful conversion is not a compatibility result.

Once the runtime is prepared, the current usage document shows .\app.exe in Windows PowerShell, or chmod +x app.elf followed by ./app.elf on Linux. This site never runs your binaries.

Controller and keyboard basics

SDL-recognized game controllers use the standard button layout. The first recognized controller is used. Keyboard and mouse bindings can be changed with an anyps5-input.ini file beside the generated executable, or through ANYPS5_INPUT_CONFIG.

Bindings omitted from that file retain their defaults. Invalid lines are reported with a filename and line number. See the full input-mapping document for supported actions and devices.