Where Does Parsec Store Config and Logs?
Where Parsec keeps its config file, session logs, and hosting approvals on Windows, macOS, and Linux.
Last updated
Parsec keeps a small data folder per OS holding config.txt, logs, and hosting state. On Windows that is %APPDATA%\Parsec, reached fastest by pasting the variable into the Explorer address bar.
Most settings never require touching these files. The in app Settings pages write to the same config.txt, so hand editing is only for advanced flags the UI does not expose. Support usually asks for the log files first. When settings reset on launch, the culprit is normally a second Parsec process holding the old config open.
Where Parsec stores this, by platform
%APPDATA%\Parsec
config.txt holds overrides, log files record sessions for support. Delete logs to save space; they regenerate. If the folder is missing, Parsec is likely running portable or never launched under this user.
~/Library/Application Support/Parsec
Same filenames as Windows under Application Support. Use Go > Go to Folder in Finder. Encoder settings here mirror the Windows flags, since most options are cross platform.
~/.config/parsec
Honors $XDG_CONFIG_HOME, defaulting to ~/.config. The Linux build is host focused, so the approved apps and virtual input data matter most here. Exact filenames may vary by release, so confirm against the running version.
Frequently asked questions
where is the parsec config file
Open config.txt in the Parsec data folder (%APPDATA%\Parsec on Windows) and add one setting per line, like app_host=1. Restart Parsec after saving. Typos are ignored silently, so copy option names exactly.
where are parsec logs for troubleshooting
In the log files beside the config (log.txt and friends). Support asks for these first because they record encoder, network, and host errors with timestamps. Delete old ones freely; Parsec recreates them on launch.
where does parsec store hosted app approvals
Under the same data root in the parsed hosting data. The approved apps list in the host settings page is the authority; the files just cache it. If a guest joins with no audio or input, re approve the app there rather than editing files.
Notice an outdated path? Let us know.