Where Does GPU Screen Recorder Store Config?
GPU Screen Recorder documents two config files under .config on Linux, with output paths passed per recording. UI config stays unverified.
Last updated
GPU Screen Recorder documents exactly two files and stays silent on the rest. An env file for the systemd service plus a portal session token, both under the app config folder. Everything else runs through command flags.
Output destinations arrive per invocation rather than from profiles. Interface defaults point at Videos in source without an official persistent path. Quote the two manual-page files and treat dotfile sightings as unconfirmed.
Where GPU Screen Recorder stores this, by platform
~/.config/gpu-screen-recorder
The two manual-documented files: systemd env vars and portal session token. No verified profiles or persistent UI config exist. Output passes through per-run flags with Videos as the common default.
Frequently asked questions
Which GPU Screen Recorder files can I back up?
The two documented files are the systemd env file and the portal restore token under the app config folder. Interface save dirs seen in dotfiles lack official standing and stay unquoted. CLI output flags decide destinations per run.
Where do recordings save by default?
Pass output file or directory flags on every invocation, since no verified profiles exist. The systemd example defaults to Videos while the interface defaults there in source. Persistent UI config paths stay unverified.
What is the restore_token file?
It holds the portal session token at its default spot. Deleting it forces fresh portal permission on next run. The env file beside it tunes the systemd service variables.
Notice an outdated path? Let us know.