01At a glance
- CPU
- PS5 x86-64 translated to host x86-64 (AVX2)
- GPU
- Vulkan 1.3 renderer, SPIR-V pipelines
- Firmware
- Official PS5UPDATE.PUP, user-supplied
- PSN
- Offline by design; no network services
02The four stages
- Translation: PS5 user code is already x86-64, so Meridian translates system interfaces and privileged behavior rather than every instruction. Hot paths require AVX2 — see CPU and AVX2.
- Rendering: GPU work is rebuilt as Vulkan 1.3 pipelines compiled to SPIR-V. The RDNA2 mapping is in RDNA2 and SPIR-V.
- System software: the official PS5UPDATE.PUP from Sony's system-software page provides system behavior, installed via File then Install Firmware — Install firmware.
- Caching: compiled pipelines persist per title. First runs hitch while the cache builds; later runs reuse it — Shader cache.
03What Meridian does not do
- No games and no firmware ship with the launcher. Own your library; 400+ titles are recognized once indexed.
- No network services. Verification is offline by design, which is why online modes are outside every rating.
- No CPU fallback below AVX2 and no renderer below Vulkan 1.3. Those floors are load-bearing.
The free Windows build is at Download Meridian.
04Questions
Q.01Why is performance good if it is emulation?
The PS5 CPU is x86-64, so translation cost is interface-level, not instruction-level. GPU cost dominates, hence Vulkan 1.3.
Q.02Why require official firmware?
System behavior must match the console. Only Sony's official PUP provides that; see System software PUP.
Q.03Why do first runs stutter?
Pipelines compile on first sight and persist. Second runs reuse them — see Shader cache.