Where Does ParaView Store Settings?
ParaView keeps settings in the OS config area, with state files and macros wherever you save them.
Last updated
ParaView stores application settings in the platform config area and nothing else automatically. Window layout, recent files, and plugin paths go there under a versioned name. Pipelines and screenshots live wherever you explicitly save them.
The version in the settings name matters. Major releases keep separate settings, so upgrading starts fresh while old entries linger. Server and client settings split in client server mode, with each side reading its own machine.
Where ParaView stores this, by platform
~/.config/ParaView
INI style settings with the ParaView version in the filename. Delete with the app closed to reset. Recorded macros default to Documents.
~/Library/Preferences/com.kitware.ParaView.plist
Preferences plist for the Kitware bundle identifier. Exact filename varies by ParaView version. Remove it with the app closed to restore defaults.
HKEY_CURRENT_USER\Software\Kitware\ParaView
Registry key for the installed version. Export it before editing. INI file mode exists but registry is the default.
Frequently asked questions
How do I share a ParaView visualization setup?
Save a .pvsm state file or Python trace script in your project folder. Settings hold window layout and recent files only. A state file plus its data reproduces the view on any machine.
How do I reset ParaView settings?
Delete the settings file or registry key for your ParaView version with the app closed. Custom macros in Documents survive. Restart rebuilds defaults, which fixes most broken layouts.
Notice an outdated path? Let us know.