VOD & Series

How VOD Updates Work: Release Timing and Refresh Rates

On-demand libraries do not update themselves — somewhere a feed drops new titles, a panel ingests them, and your player re-fetches its catalog according to its own refresh clock. The delay you see between it should be there and it is there is the sum of those timings, and each one is tunable. This guide walks through where new entries come from, when each layer refreshes, and why your client sometimes shows a stale shelf that a pull-to-refresh would have fixed instantly.

7days: how often some panels drop content packages
2clocks: server ingest vs client re-fetch
0app reboots needed when the pipeline is healthy
24-48htypical shelf-to-release latency on a live cadence

Where new titles come from

A provider's VOD fills from upstream feeds — content packages that arrive on a schedule with metadata and stream URLs already attached, or titles the provider adds by hand between feeds. Most panels support both: automated ingests for volume, manual overrides for quality.

The feed's drop cadence decides the baseline: some packages land daily, others weekly, and the panel only knows what the latest package contained. A title that should be live is live only after the next drop and the next ingest pass.

Ingestion is also where cleanup happens — deduplication, matching against a series database, artwork backfill — which is why a fast feed can still climb the shelf slowly when the enrich step is thorough.

When the catalog refreshes

Most panels re-ingest on a set schedule rather than continuously, and the resulting catalog is what players later pull. If your provider adds films on Wednesdays, an update arriving Thursday is the system working to its rhythm, not lag.

The server-side refresh and the player-side sync are separate clocks: the server updates its list when it ingests; your client updates its list when it next re-fetches — which may be hours later or on next launch.

The two clocks explain almost every it-exists-but-I-cannot-see-it report. The debug path is to check twice: once in a second player to prove the server updated, and once after a manual refresh to prove the client syncs.

What your player refreshes — and what it does not

A typical client refresh re-fetches the catalog: lists, categories, artwork and metadata. What it usually does not do is re-download artwork binaries unless they changed, or re-pull details for titles already cached locally.

Watch history and favorites are stored client-side, so a refresh that churns entry IDs silently detaches them — your movies stay but their checkmarks vanish. That is why stable IDs matter for library updates.

Knowing that scope makes your expectations honest: refresh the catalog when the shelf looks stale, but do not expect it to repair data the server feeds wrong — that is upstream work.

Why 'stale shelf' happens

The classic stale shelf is a client clock mismatch: the player fetched its catalog yesterday, the server added a film today, and nobody told the client. Launching the app does not always trigger a re-fetch, so the old list persists.

Less visibly, panels occasionally ingest the same title twice under two IDs between refreshes, producing duplicates you cannot fix client-side at all. That is a server hygiene issue, and the shelf keeps showing it until the panel cleans house.

Finally, some players cache artwork aggressively; you can see the new title's row while the poster stays blank — a client cache problem, cured by a deep refresh of the app's image cache.

Force-refreshing without breaking watch state

Every serious player offers a manual refresh — often a long-press on the section or a menu item — which forces a catalog re-fetch without touching your favorites or history. That is the correct tool for the stale shelf.

The heavier hammer is deleting and re-adding the playlist, which rebuilds everything from scratch but resets layout preferences and, in some clients, resets view positions. Reserve it for when a manual refresh visibly fails.

A clean middle path is the app's own cache-clear for images only: it re-downloads artwork without re-syncing the catalog, fixing blank boxes while leaving watch state alone.

Read the library age like a health check

A healthy library has visible movement: recent additions appear within a day or two of release, artwork fills in, and the recently-added shelf is fresh. A frozen shelf says the pipeline upstream is stalled.

Check the provider's refresh rhythm deliberately: if the this-week shelf is empty for three weeks in a row, the feed is failing at the source rather than your client being slow — and no amount of app fiddling fixes a dead ingest.

IPTVXtream keeps the ingest pipeline on a cadence with release timing, so new additions land on the shelf quickly and the library stays current without you babysitting refresh buttons. That consistency is the quiet half of library quality.

Frequently asked questions

How often should my library update?

With a healthy provider and player, within a day or two of a title's release — one ingest pass plus one client re-fetch covers the latency.

Why did a new movie not appear on my shelf?

Check two things: a second player to test the server, then a manual refresh to test the client. One of them will be the culprit.

Do updates remove my watch history?

They should not — history is client-side and survives catalog refreshes unless entry IDs churn upstream.

Can I be first to see new titles?

Some players sort by release date or keep a recently-added shelf; set that as your default and the new content floats to the top.

The bottom line

VOD freshness is two clocks cooperating: the server's ingest and your player's re-fetch, with tuneable latency between them. When the shelf looks stale, measure both before touching anything, and treat a permanently frozen library as an upstream health problem rather than an app quirk. On our side the pipeline runs on cadence, so new titles land without babysitting. If your current provider makes you refresh by hand, message us on WhatsApp at +1 (555) 364-8853 and we will show you the difference on a trial.

Ready to test it yourself?

Start a free trial and judge the quality with your own eyes.

Start Free Trial on WhatsApp
JB
Jordan BlakeFounder & Protocol Engineer · IPTVXtream

Jordan is a software engineer who spent years building streaming infrastructure before founding IPTVXtream. He designed our routing stack, EPG pipeline and failover systems — and still answers edge-case questions on WhatsApp himself.