starred/shadPS4

Fork 0

mirror of https://github.com/shadps4-emu/shadPS4.git synced 2026-04-26 08:15:59 +03:00

[GH-ISSUE #3856] [Feature Request]: a true portable shadPS4 #1155

New issue

Closed

opened 2026-02-27 21:10:14 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 21:10:14 +03:00

Owner

Originally created by @hellomynameisnone on GitHub (Dec 6, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3856

Checklist

I have searched for a similar issue in this repository and did not find one.

Description

With the implementation of the QT launcher, the option to make shadPS4 portable is no longer possible.

Previously, we could make it portable by modifying the config.toml file. However, now all configuration files, logs, input_config, etc., are always stored in C:\Users[USERNAME]\AppData\Roaming\shadPS4.

If you delete that folder, shadPS4 will detect it as a first launch and you will need to reconfigure everything.

The Settings > User > Create User Folder option does not change this situation, as everything still depends on the AppData folder.

Reason

Reasons to Make shadPS4 Portable

Easier to Move Between Computers

A portable version allows users to place shadPS4 on a USB drive or external SSD and run it on any PC without reinstalling or reconfiguring.
Right now, because it depends on AppData, users must manually recreate settings on every machine.

No Forced Use of AppData

Some users prefer to avoid putting large files, logs, or configs in AppData, especially when using small system SSDs.
A portable mode keeps everything inside the emulator's own folder, giving the user full control.

Backup and Restore Simplicity

With a portable layout, you can back up your entire shadPS4 setup by copying a single folder.
Currently, configs and data are split between the program folder and AppData, making backups more inconvenient.

Cleaner and More Organized Installation

A portable mode avoids cluttering the system with extra directories and leftover files.
Users who like to keep their software self-contained benefit from this cleaner approach.

Useful for Testing or Multiple Installations

Developers, testers, or advanced users might want multiple separate instances of shadPS4 with different settings.
This is almost impossible when all instances point to the same AppData directory.

Ideal for Sandbox, Offline, or Restricted Environments

Some users run emulators in:

Sandboxed environments

Offline machines

Custom directory structures
A portable mode works seamlessly in these setups, while AppData-dependent software can fail or cause permission issues.

Reduces Risk of Configuration Loss

Right now, deleting the AppData folder resets everything to first-launch state.
A portable mode keeps all configs local, making accidental loss far less likely.

More Consistent With How Other Emulators Work

Most major emulators (RPCS3, Cemu, Dolphin, Yuzu, Ryujinx, etc.) support portable operation.
Users expect shadPS4 to behave similarly for convenience and familiarity.

Examples

No response

Originally created by @hellomynameisnone on GitHub (Dec 6, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3856 ### Checklist - [x] I have searched for a similar issue in this repository and did not find one. ### Description With the implementation of the QT launcher, the option to make shadPS4 portable is no longer possible. Previously, we could make it portable by modifying the config.toml file. However, now all configuration files, logs, input_config, etc., are always stored in C:\Users[USERNAME]\AppData\Roaming\shadPS4. If you delete that folder, shadPS4 will detect it as a first launch and you will need to reconfigure everything. The Settings > User > Create User Folder option does not change this situation, as everything still depends on the AppData folder. ### Reason Reasons to Make shadPS4 Portable 1. Easier to Move Between Computers A portable version allows users to place shadPS4 on a USB drive or external SSD and run it on any PC without reinstalling or reconfiguring. Right now, because it depends on AppData, users must manually recreate settings on every machine. 2. No Forced Use of AppData Some users prefer to avoid putting large files, logs, or configs in AppData, especially when using small system SSDs. A portable mode keeps everything inside the emulator's own folder, giving the user full control. 3. Backup and Restore Simplicity With a portable layout, you can back up your entire shadPS4 setup by copying a single folder. Currently, configs and data are split between the program folder and AppData, making backups more inconvenient. 4. Cleaner and More Organized Installation A portable mode avoids cluttering the system with extra directories and leftover files. Users who like to keep their software self-contained benefit from this cleaner approach. 5. Useful for Testing or Multiple Installations Developers, testers, or advanced users might want multiple separate instances of shadPS4 with different settings. This is almost impossible when all instances point to the same AppData directory. 6. Ideal for Sandbox, Offline, or Restricted Environments Some users run emulators in: Sandboxed environments Offline machines Custom directory structures A portable mode works seamlessly in these setups, while AppData-dependent software can fail or cause permission issues. 7. Reduces Risk of Configuration Loss Right now, deleting the AppData folder resets everything to first-launch state. A portable mode keeps all configs local, making accidental loss far less likely. 8. More Consistent With How Other Emulators Work Most major emulators (RPCS3, Cemu, Dolphin, Yuzu, Ryujinx, etc.) support portable operation. Users expect shadPS4 to behave similarly for convenience and familiarity. ### Examples _No response_

kerem closed this issue

2026-02-27 21:10:14 +03:00

kerem commented

2026-02-27 21:10:15 +03:00

Author

Owner

@RuskyDed commented on GitHub (Dec 6, 2025):

Please read this:
https://github.com/shadps4-emu/shadps4-qtlauncher/issues/171

@RuskyDed commented on GitHub (Dec 6, 2025): Please read this: https://github.com/shadps4-emu/shadps4-qtlauncher/issues/171

kerem commented

2026-02-27 21:10:15 +03:00

Author

Owner

@StevenMiller123 commented on GitHub (Dec 6, 2025):

The shadPS4 core is already portable (if a folder named user is by the shadPS4 executable, that is used instead of AppData).

Unless I'm mistaken, this is effectively a duplicate of https://github.com/shadps4-emu/shadps4-qtlauncher/issues/171

@StevenMiller123 commented on GitHub (Dec 6, 2025): The shadPS4 core is already portable (if a folder named user is by the shadPS4 executable, that is used instead of AppData). Unless I'm mistaken, this is effectively a duplicate of https://github.com/shadps4-emu/shadps4-qtlauncher/issues/171