Where Are Jupyter Config and Data Files Stored?
Jupyter keeps configuration in a user config folder and kernels, extensions, and data files in a separate data folder. Transient connection and server files live under a runtime subfolder.
Last updated
Config covers files such as jupyter_notebook_config.py and lab settings. Data covers kernelspecs, nbextensions, and shared assets.
Locations follow platform conventions and can be changed with environment variables. The paths command prints the config, data, and runtime folders in use.
Where Jupyter stores this, by platform
~/.jupyter/jupyter_notebook_config.py
User config defaults to ~/.jupyter. User data defaults to ~/.local/share/jupyter and respects XDG_DATA_HOME. Runtime defaults to a runtime subfolder under user data. Override with JUPYTER_CONFIG_DIR, JUPYTER_DATA_DIR, JUPYTER_PATH, and JUPYTER_RUNTIME_DIR. System data also appears under sys prefix share and under local and system share folders.
~/.jupyter/jupyter_notebook_config.py
User config defaults to ~/.jupyter. User data defaults to ~/Library/Jupyter. Runtime defaults to a runtime subfolder under user data. Override with JUPYTER_CONFIG_DIR and related variables. System paths include sys prefix etc/jupyter and share/jupyter.
C:\Users\<user>\.jupyter\jupyter_notebook_config.py
Replace <user> with the Windows account name. User data defaults to AppData Roaming jupyter. Runtime defaults to a runtime subfolder under user data. System config and data live under PROGRAMDATA jupyter. Use the paths, config dir, data dir, and runtime dir queries to print exact locations.
Frequently asked questions
How do I generate the main config file?
Run jupyter notebook with the generate config action to write jupyter_notebook_config.py into the config folder. Edit the file to set server traits. Repeat with the server config name for Jupyter Server options.
Why is Jupyter not seeing my kernel?
Kernels are found through the data search path, not only the user data folder. Env installs register under sys prefix share/jupyter/kernels. Check the data list from the paths command and confirm the kernels subfolder holds a valid kernelspec.
Notice an outdated path? Let us know.