Identify whether the timing data exists
A server can play an episode without knowing which seconds form its intro or recap. Jellyfin’s media-segment system stores typed time ranges rather than simply treating every chapter as an intro. Before looking for a missing skip button, determine whether an appropriate provider has supplied segment data for the intended item.
Use the documented preparation chain
Jellyfin introduced media segments in 10.10. Its guide describes installing a provider, running the media-segment scan and choosing client actions for the supported segment types. The official Chapter Segments Provider can derive segments from chapter names. Clients decide how to use the supplied information, so completing a server scan does not itself prove that every player will show or automatically activate the same control.
Check one authorised episode across the chain
For example, an administrator can inspect a known episode’s segment preparation and then review the intended client’s playback preference. Keep the provider, scan result and client action as separate observations. If the timing is wrong, identify the particular range rather than enabling automatic skipping across an entire library without review. A button appearing is not a guarantee that the detected boundary matches the viewer’s preferred stopping point. If no button appears, report whether data is absent or a prepared segment is not exposed by that client. Those questions require different fixes and should not start with replacing the video file.
Questions, answered
Does running a segment scan force identical skip behaviour on every client?
No. Jellyfin says clients decide how to act on the supplied segment information.