How to Uninstall Kodi Repositories the Right Way

Kodi is awesome… right up until your “Add-ons” section looks like a junk drawer stuffed with mystery keys, expired coupons,
and a remote you swear you didn’t own yesterday. If you’ve installed a few third-party repos over time (or inherited a setup
from a friend who “totally knows what they’re doing”), uninstalling Kodi repositories correctly can save you from broken updates,
weird errors, and unnecessary clutter.

This guide walks you through the right way to remove Kodi repositories: uninstall the repo, remove its file source,
clean up leftover packages, and (carefully) handle dependencies. You’ll also learn what not to delete so you don’t accidentally
nuke the add-ons you still use.

First: Know What You’re Removing (Repo vs. Add-on vs. Source)

Before we start uninstalling things with the confidence of a toddler “helping” you clean the kitchen, let’s define four terms
that Kodi users often mix up:

• Repository (repo): A catalog of add-ons. Kodi checks it for updates and lets you install add-ons from it.
• Add-on: The actual thing you use (video add-on, program add-on, skin, service, etc.).
• File Manager source: A “saved location” (URL/path) you add so Kodi can access a repo ZIP or files.
• Packages: Cached ZIP files Kodi downloads during installs/updates (useful… until they pile up).

Here’s the key idea: Uninstalling a repository does not automatically remove its add-ons, and removing a File Manager
source does not remove the repo that was installed from it. To uninstall Kodi repositories “the right way,” you’ll usually do
both.

Quick Safety Checklist (2 Minutes That Can Save You 2 Hours)

1) Identify what you still need

If you uninstall a repo that feeds updates to an add-on you rely on, that add-on might still runbut it won’t update from that
repo anymore. Make a quick list of what you still use and what you don’t.

2) Consider a simple backup

If your Kodi setup is precious (custom skin, library, profiles, advanced settings), back up your Kodi data folder before deep-cleaning.
Even a quick copy of the folder can be a lifesaver if you remove the wrong dependency.

3) Keep it legal and clean

Kodi itself is legal, and the official repo includes plenty of legitimate add-ons. But third-party repositories can be taken over,
abandoned, or become unsafe over time. Cleaning out repos you don’t need is a smart security habit.

Step-by-Step: Uninstall the Repository in Kodi (The “Correct” Core Step)

These menu names can vary slightly by Kodi version/skin, but the path is usually very close to this:

1. From Kodi Home, go to Add-ons.
2. Select My add-ons.
3. Choose Add-on repository.
4. Highlight the repository you want to remove.
5. Open the Information screen (or context menu) and select Uninstall.
6. Confirm.

Tip: On many devices, the “context menu” is triggered by a long-press, right-click, keyboard “C,” or a remote menu button.
If you’re using a skin with different navigation, look for “Information” or a small options menu on the repo item.

What if you don’t see “Uninstall”?

• It may be the official Kodi repository. You generally can’t remove core/official components the same way.
  (You can still manage updates and add-ons through settings.)
• You might be looking at the install source, not the installed repo. Double-check you’re under
  My add-ons → Add-on repository, not “Install from zip file.”
• Something depends on it. Uninstall add-ons from that repo first (next section), then return to remove the repo.

Don’t Skip This: Remove the Repo’s File Manager Source

Even after you uninstall a repository, Kodi can still keep the original File Manager source you added to install it.
Leaving old sources behind is how you end up with a “Source List Museum.”

Remove the source

1. Go to Settings (gear icon).
2. Select File Manager.
3. Find the source name you added for that repo (often a short nickname).
4. Highlight it, open the context menu, and choose Remove source.
5. Confirm.

Why this matters: Old sources can cause confusion later (“Which of these 12 ‘repo’ sources is the real one?”),
and you’re less likely to reinstall something by mistake.

Clean Up Related Add-ons (Optional, But Often the Real Goal)

Many people remove a Kodi repo because they don’t want the add-ons from it anymore (or the repo stopped working).
If that’s you, don’t stop at uninstalling the repositoryremove the add-ons you no longer use.

Uninstall add-ons installed from a repo

1. Go to Add-ons → My add-ons.
2. Browse by category (Video add-ons, Program add-ons, Services, Skins, etc.).
3. Select the add-on you no longer want.
4. Choose Uninstall (or disable first if you’re unsure).

Good to know: If you remove the repository but keep the add-on, the add-on may still run, but you’ll lose easy updates from that repo.
That can be fine for a stable tool you rarely changebut it can also lead to “Why did this suddenly break?” moments later.

Handle Dependencies the Smart Way (Don’t Rage-Delete Libraries)

Dependencies are support add-ons that other add-ons need. Kodi can leave behind unused (“orphaned”) dependencies after you uninstall a skin or plugin.
The good news: Kodi can help you identify what’s safe to remove.

Find and remove orphaned dependencies

1. Go to Settings → System.
2. Select Add-ons.
3. Choose Manage dependencies.
4. Look for items marked Orphaned (no longer required).
5. Uninstall orphaned items individually, or use Remove all orphaned add-ons if your Kodi version offers it.

Be careful: Some dependencies are shared by multiple add-ons. If something is not marked orphaned, it may still be needed.
When in doubt, disable firstor remove only what Kodi flags as orphaned.

Clean Leftover Files: Packages and Add-on Data

If Kodi feels “heavier” over time, it’s often because of leftover ZIPs and settings folders. This is where a clean uninstall of Kodi repositories
becomes a proper spring cleaning.

1) Clear the “packages” cache (safe housekeeping)

Kodi stores downloaded install/update ZIPs in the addons/packages folder. This can grow large, especially on limited-storage devices
like Fire TV sticks or Android TV boxes.

Using Kodi’s built-in File Manager, you can navigate to your Kodi data area via special://home and delete old ZIPs.
The typical path is:

• special://home/addons/packages

If you prefer file browsing outside Kodi, the exact folder location depends on your platform. Kodi documents the data folder locations by OS, and many
users simply clear the packages folder periodically when troubleshooting install/update issues or freeing space.

2) Remove leftover add-on settings (only for add-ons you truly removed)

Even after uninstalling an add-on, Kodi may keep its settings and cached files under:

• special://home/userdata/addon_data

If you’re removing a repo and its add-ons completely, deleting the corresponding folder inside addon_data can remove old settings,
logins, and cached configuration. Just make sure the add-on is actually gone firstotherwise you’ll “reset” it unexpectedly.

Advanced: When a Repo or Source Won’t Go Away

Sometimes Kodi refuses to cooperate. Here are common real-world causes and fixes.

Problem: “Uninstall” is blocked or the repo returns after restart

• Something keeps reinstalling it (a build, wizard, or maintenance tool). Disable/remove that tool first, then uninstall the repo again.
• An add-on still depends on it. Remove add-ons installed from that repository, then retry uninstalling the repo.

Problem: You can’t find the source to remove, but Kodi still lists it

If a source entry is stuck (especially after network changes), it may live in Kodi’s configuration files (for example, sources.xml).
Editing configuration files is a last resortdo it only if you’ve backed up your Kodi data folder.

Aftercare: Keep Kodi Clean Going Forward

Turn off Unknown Sources when you don’t need it

Enabling “Unknown sources” is what allows installing from ZIP files. If you’re done installing third-party repos, consider turning it off again.
It’s a simple safety habit that reduces accidental installs and lowers risk from untrusted sources.

Check add-on update behavior

Kodi includes settings that control where official add-ons should update from when duplicates exist in multiple repositories.
If you’ve installed third-party repos in the past, review your add-on update settings so you know which repository is “winning” updates.

Keep only what you actively use

A tidy Kodi setup is usually faster, easier to troubleshoot, and less likely to break. If you haven’t used a repository in months, it’s probably not a
“collection”it’s clutter wearing a fancy hat.

FAQ: Fast Answers to Common Repo-Removal Questions

Will uninstalling a Kodi repository delete my add-ons?

Not automatically. Removing a repository usually removes the catalog and update source, but installed add-ons may remain until you uninstall them.

Will my add-ons still work after I remove the repo?

Often yesuntil an add-on needs an update or a dependency changes. If it’s something you rely on, consider keeping a trusted update source (preferably the official repo where applicable).

Does removing a repository delete my library or media files?

No. Your local media files aren’t removed by uninstalling repositories. You’re only changing add-on sources and related configuration.

When should I consider a full Kodi reset?

If you’re stuck in a loop of dependency errors, broken installs, and random crashes after heavy add-on experimentation, a clean start (back up first!) may be faster than endless troubleshooting.

Real-World Cleanup Experiences (So You Don’t Repeat Everyone Else’s Mistakes)

If you’ve ever tried to uninstall Kodi repositories and thought, “That was easy,” congratulationsyou are a rare and magical creature.
In real setups, repo removal often turns into a little detective story. Here are common patterns people run into, plus what works in practice.

The “Repo Closet” Problem: Too Many Sources, Not Enough Context

A lot of Kodi users add File Manager sources with names like “repo,” “newrepo,” “zip,” or the timeless classic “123.” Months later, you’re staring at
File Manager like it’s a word search puzzle: Which one of these is the source I should remove?
The fix is boring but effective: after uninstalling a repository, immediately remove its File Manager source and rename any remaining sources to something meaningful
(example: “Smithsonian,” “LocalNAS,” “KodiOfficialBackup”). Your future self will send you a thank-you card.

The “Zombie Add-on” Surprise: The Repo Is Gone, But Stuff Still Runs

This one confuses people: you uninstall a repo, restart Kodi, and your add-on still shows up and even launches. That’s normalbecause the add-on is installed locally.
The catch is updates. A “zombie add-on” can work perfectly for a while, then fail later when a service changes or a dependency updates.
The smart play is to decide: do you want that add-on long-term? If yes, make sure it updates from a trusted source (ideally the official repo when available).
If no, uninstall it now while you still remember why you were cleaning house in the first place.

The “Dependency Domino” Trap: Deleting Libraries Like They Owe You Money

It’s tempting to delete every dependency you see. Resist that urge.
In many real cleanups, people remove a repo, then start uninstalling dependencies at random, and suddenly a totally unrelated add-on breaks.
The safer approach is to use Kodi’s orphaned labels as your guide: remove only what Kodi identifies as orphaned, or uninstall dependencies only when you’re sure nothing else uses them.
Think of dependencies like shared plumbing: you don’t rip out pipes because you replaced one faucet.

The “Storage Panic” Moment on Fire TV/Android TV

On smaller devices, uninstalling repositories is often motivated by a storage warningKodi gets blamed, and sometimes unfairly.
What commonly helps is clearing the accumulated ZIP files in the addons/packages cache. Those leftover install files can quietly grow over time,
especially if you’ve experimented with multiple repos and frequent updates. In real cleanups, deleting old packages can free noticeable space without harming your working add-ons.
Combine that with removing unused repos and their add-ons, and Kodi stops feeling like it’s dragging a suitcase full of bricks.

The “It Came Back” Mystery: Repos Reappearing After You Remove Them

When a removed repository reappears, it’s usually not Kodi being hauntedit’s another add-on doing “helpful” things in the background.
Some build/maintenance tools and config add-ons can reinstall repos or re-add sources on startup. The practical fix is to remove the installer tool first,
then remove the repo again, then reboot. If you keep your setup simple (fewer repos, fewer “maintenance” add-ons), this problem largely disappears.

The big lesson from real-world repo cleanups is that the repository is only one piece. If you uninstall the repo but leave the source,
the add-ons, the packages cache, and orphaned dependencies behind, you haven’t really cleanedKodi just looks cleaner from across the room.
Do the full loop once (repo → source → add-ons → orphaned dependencies → packages), and future maintenance becomes quick and painless.