Where Does Nemo Store Actions and Settings?
Nemo actions live as .nemo_action files in local share nemo actions. Prefs are dconf, favorites in gvfs-metadata.
Last updated
Nemo splits customization three ways. Context menu actions are keyfiles ending in .nemo_action, scanned from system and user data dirs, with the user folder winning. Preferences live in dconf under the nemo schemas.
Favorites and pins are neither. They attach as file metadata in the gvfs-metadata store, which explains why wiping config never clears them. Scripts from the Nautilus era do not apply; Nemo uses actions instead. The sample action file in system files documents every available key.
Where Nemo stores this, by platform
/home/<username>/.local/share/nemo/actions
User context actions. Each file is an INI style keyfile with Exec, Selection, and Extensions keys.
/home/<username>/.local/share/gvfs-metadata
Favorite and pinned metadata for files. Travels with the gvfs store, not with dconf settings.
Frequently asked questions
How do I add a Nemo context action?
Drop a nemo_action text file into the actions folder and restart Nemo with nemo q. The sample action in system files documents every key.
Where are Nemo favorites stored?
Favorites are file metadata in gvfs-metadata, not a text list. Move the metadata store with the files to keep stars attached.
Notice an outdated path? Let us know.