No. A player/backend can buffer an active session for timeshifting, while catch-up retrieves an earlier programme through a separate supported replay route.
8K IPTV · guides
A practical next step

Catch-up is not the same as VOD
Replay from a live channel and an on-demand title are different viewing paths.
Use the controls and account conditions that apply to your actual setup.
Read the full details
Catch-up is not the same as VOD
Replay from a live channel and an on-demand title are different viewing paths.
Identify the path you opened
Check that programme’s replay marker
Do not infer a universal replay window
Use the controls and account conditions that apply to your actual setup.
OPEN THE 8K IPTV GUIDE
HELP & SETUP
KNOW THE DIFFERENCE
Catch-up is not the
same as VOD
Replay from a live channel and an on-demand title are different
viewing paths.
01
02
03
Catch-up is not the same as
VOD
Why this happens
Pausing a channel you are already watching can rely on a buffer created during that viewing session. Catch-up begins with a programme that was broadcast earlier, possibly before the player was open. Those are different capabilities even if both let you watch behind the live moment. Closing a session or changing channels may affect a local timeshift buffer, whereas a provider replay window follows its own rules. Neither feature should be inferred just from the presence of a pause icon.
Identify whether the player is working with a local/backend timeshift buffer or opening a programme from the guide’s replay controls. Kodi’s PVR documentation describes timeshifting as backend-dependent and its specific add-on documentation can define buffer behavior for that route. That does not establish the same behavior for every IPTV application. Test each function separately on the device you intend to use, and keep an important live event in mind before assuming a paused session will survive a channel change or restart. The labels may be similar while the stored media and limits are quite different.
A useful way to work through it
Describe whether playback was paused during an active live session or opened from a past listing.
Read the player’s/backend’s own timeshift and replay guidance.
Avoid assuming a local pause buffer survives closing the app or changing channels.