# How to use AnyPS5

Treat setup as three separate jobs: prepare the tool, convert the input, then assemble the runtime. Keep a record at each stage so a failure has a useful starting point.

Canonical: https://anyps5.fun/getting-started/
Documentation reviewed: 2026-10-14

## 01 / Choose your route

The native relinker gives you a terminal workflow. The upstream browser converter offers a local file-selection workflow. This site explains those routes; it does not convert or collect your files.

- Start with the download guide and keep the release tag or source revision in your notes.
- Use the instructions for your actual tool version. A newer main-branch flag may not exist in an older release.
- Keep the original input in a separate folder and write conversion output elsewhere.

## 02 / Check the input

Upstream documents a clean ELF input and bundled module directories beside it. SELF containers need preparation before conversion. Follow the upstream input rules rather than changing a file extension.

Use a short, easy-to-find workspace for your first attempt. Record the executable name and module folder before running the command. A missing input is a setup issue; it does not tell you whether a game is compatible.

## 03 / Convert for the target OS

### Windows output

```text
relinker --windows source/input.elf app.exe
```

### Linux output

```text
relinker source/input.elf app.elf
```

These examples follow the reviewed main-branch usage document. Check relinker --help in the build you downloaded. Choosing a filename alone is not a substitute for selecting the output format.

## 04 / Assemble and launch

| Location | Purpose |
| --- | --- |
| libs/ | AnyPS5 host system libraries |
| app0/ | Application resources and converted guest modules |
| app.exe or app.elf | Converted entry executable |

The architecture separates host replacements from converted guest modules. Use the generated module paths from the conversion log. Preserve a copy of that log alongside your setup notes.

Launch from a terminal so you can keep the first failure message. Next, use the troubleshooting guide to decide whether the failure belongs to conversion, loading or runtime behavior.

## 05 / Record a useful result

- Write down the release or commit, OS, CPU, GPU and driver.
- Describe the exact point reached: conversion, window, menu or a specific gameplay scene.
- Save the complete first error and the command that produced it.
- Change one variable, repeat the same test and compare the result.

## Common questions

### Does conversion mean a game will run?

No. The upstream converter explicitly separates conversion from runtime compatibility.

### Where should I go after a startup failure?

Open the troubleshooting guide and identify the first failing stage before changing settings.

## Sources

- [Relinker usage](https://github.com/boykopovar/AnyPS5/blob/main/docs/user/USAGE.md) — reviewed 2026-10-14
- [Architecture](https://github.com/boykopovar/AnyPS5/blob/main/docs/dev/ARCHITECTURE.md) — reviewed 2026-10-14
- [Upstream browser converter](https://boykopovar.github.io/AnyPS5/) — reviewed 2026-10-14