List the assets the backup must recover
A working Kodi setup contains more than the executable. Before choosing a backup method, list the sources, settings, add-ons, playlists and library state you want to recover. Keep the original media as a separate asset. A configuration backup cannot be assumed to contain every movie or recording stored elsewhere.
Record the operating system, Kodi version and installation type. An ordinary Windows installation, a portable build and a packaged Linux application can use different data locations. Use the actual installation’s documented path rather than backing up whichever folder happens to contain the application icon.
Identify program and data locations
Kodi’s backup guide distinguishes the core installation folder from the Kodi data folder, which holds subsequent settings and usage data. The latter is the parent of Userdata. Locate it using the current platform table and confirm it contains the expected setup information.
Choose a backup destination outside the active data directory and keep an independent copy where your recovery needs require it. Preserve the existing setup while making the copy. If storage access on a television is restricted, use a supported file-management or backup route rather than guessing an Android directory from another device.
Plan for the actual recovery combination
The developer cautions against treating a full data-folder copy as a transfer between different operating systems or major Kodi versions. Keep the intended recovery target aligned with the documented method. A library-export workflow may serve a different goal from reproducing the entire application state.
For an original plan, recovery to the same box and version after a failed setting change is a different project from moving a collection from Windows to another platform. Write that goal down before deciding which files and method to use. Avoid assuming a backup is portable merely because its directory can be copied.
Verify coverage before depending on the backup
Inspect the copied folder and retain its date, version and source-device identity. Keep separate protection for the actual media and any custom assets that must remain recoverable. A successful file-copy dialog is useful evidence but does not establish that a restoration has been tested.
Prepare a recovery checklist with one library item, a source connection and a harmless setting. If you later perform a controlled restore, assess those observations explicitly. The expected outcome here is a known backup scope and recovery plan, not an unperformed restore claim or a promise that every add-on dependency will remain available forever.
Questions answered
Is backing up Kodi’s executable enough to preserve my setup?
No. Identify the actual data folder and the state you need to recover. Program installation and configuration are different assets.
Does a Kodi data-folder copy include external films automatically?
No. Treat original media protection separately and verify the documented coverage of the chosen method.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.