Distinguish a segment from an ordinary chapter
Jellyfin describes media segments as timed metadata with a type, such as intro, recap or outro. This is different from an ordinary chapter marker without a segment type. A file having chapters does not by itself establish that a client will show an intro-skip button for the relevant section.
Choose one episode you control and note the portion you expect to skip. Keep the exact edition and file fixed because different cuts can have different timing. A skip control that targets the wrong interval is a metadata accuracy issue; a control that never appears may concern segment creation or the client’s handling of that data.
Establish the segment-producing route
Jellyfin’s documented process begins with a media-segment provider. Its official Chapter Segments Provider can create segments based on chapters and their names. Install only the provider that matches your intended approach and review its current configuration. An unrelated metadata plug-in does not automatically establish intro detection.
Use a small, representative library item first. Inspect whether its source chapters or provider inputs actually distinguish the section you want to mark. If no suitable input exists, merely installing a provider may not create useful boundaries. Avoid labelling every first chapter an intro without checking the content and the provider’s documented behavior.
Run the appropriate scan and inspect the same item
The developer documentation identifies a Media segment scan task in the dashboard for immediate creation, with background operation also available. Run the appropriate task after configuring the provider and let it complete before assessing the client. A normal library title appearing does not prove that this separate metadata task has produced segments.
Return to the same episode and keep its file version unchanged. If timing is incorrect, record the expected interval and the observed behavior. Repeating a broad scan without checking the provider input can reproduce the same wrong result. Diagnose data creation before repeatedly reinstalling the television client.
Configure the client’s action separately
Jellyfin stores segment information and supplies it to clients; clients decide which actions to offer. Inspect the current client’s playback settings and support for the relevant segment type. A server-side segment does not guarantee identical buttons on every client or version.
Test the same item through the intended client and record whether a control appears, whether it is automatic or manual, and whether it moves to the intended boundary. Keep segment metadata and client action as two checkpoints in the case. The result should be a verified route for your actual combination, not a blanket promise that all Jellyfin devices can skip every intro or commercial.
Questions answered
Why do chapters not automatically produce an intro-skip button?
Chapters and typed media segments are different. The provider must create usable segment data, and the client must support an action for that data.
Does a completed library scan prove segment creation finished?
Not necessarily. Jellyfin documents a separate Media segment scan task. Check that process and the configured provider before testing the client action.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.