IPTV Simple Client is an add-on built into Kodi that reads two separate files: a playlist (usually an M3U file, a plain text list of channel names and stream addresses) and an EPG file (usually XMLTV, the schedule data showing what's on each channel). The add-on itself doesn't store or supply any channels — it just points at whatever URLs you gave it in settings. When people say it's 'not loading channels,' the fault is almost always in one of those two source files or the URL pointing to them, not in the add-on's code itself.

Playlist URLs sometimes rotate or expire on the provider side without warning, so a link that worked yesterday can return an empty or broken file today. If the refresh interval in Kodi's settings is set to a long window, the add-on won't notice the change until its next scheduled check, which can leave you staring at a blank or frozen list for hours even though the underlying source has already been fixed. Manually forcing a refresh, or shortening the interval in settings, is usually the fastest way to confirm whether the source URL itself is the problem rather than something wrong with the add-on's configuration.

Player apps, including Kodi add-ons, hold the entire channel list in memory while running, and that memory load climbs as the list grows. Lists that push past roughly 18,000 visible channels start to destabilize some players during load, which can look like the app hanging or failing partway through rather than a broken playlist. This is a different failure than an expired URL, since the playlist loads fine but the app struggles to hold all of it at once. Hiding channel groups you don't watch trims what the add-on has to hold in memory, and it's a real fix for this specific cause, not a workaround for something else.

Two changes help more than most others: setting the stream buffer to none or minimal so the add-on doesn't wait on a large pre-buffer before it even attempts to load, and switching to a public DNS resolver so playlist and stream URLs resolve reliably instead of timing out. Neither one is a guess — both target a specific, common failure point in how the add-on fetches its source files over the network. If channels still won't load after both changes, the playlist URL itself, or the file it points to, is the more likely remaining cause worth checking directly.