Where Is the VisiData Config File?
VisiData reads ~/.visidatarc on every launch for Python based configuration, keybindings, and plugin loading across Linux, Mac, and Windows.
Last updated
VisiData configures itself through ~/.visidatarc, a Python file executed at startup on every platform. Options, theme tweaks, keybindings, and plugin imports all live there together. No registry or dconf participates.
That single file portability suits data workflows across machines. Copy it plus any helper scripts and the sheet experience reproduces exactly. Version upgrades occasionally rename options, so check the changelog when binds misbehave after updating.
Where VisiData stores this, by platform
~/.visidatarc
Python startup config for options, binds, colors, and plugin imports. Same path across supported platforms. Restart to apply edits.
~/.visidatarc
Same visidatarc layout as Linux for Mac installs. Plugin imports resolve through Python paths. One file carries the whole setup.
%USERPROFILE%\.visidatarc
Windows builds read the same home relative config name. Python based plugins load identically. Keep helper scripts beside it.
Frequently asked questions
Where do VisiData settings go?
Copy the documented example into ~/.visidatarc and edit options, colors, and binds there. Python code runs at startup so plugins load from the same file. Restart VisiData to apply changes.
How do I load VisiData plugins?
Add the plugin import lines to ~/.visidatarc so they load each session. Keep third party plugin files where Python finds them. The file doubles as config and loader, which keeps setups in one place.
Notice an outdated path? Let us know.