Keep the film and moment constant
Choose a short permitted passage and note the initial audio, video and subtitle selections. Compare the same item with subtitles off and then with the required track on. Make this a brief agreed diagnostic step, keeping an accessible viewing alternative available for anyone who relies on captions.
Do not compare one film without subtitles with a different film that includes them. That changes the codec, bitrate, container and content together. The useful observation is whether the selected text track changes this exact item’s playback behaviour in this exact client.
Read the server’s actual processing state
Ask the authorised server operator to inspect the playback information. Jellyfin distinguishes direct playback from media conversion; a subtitle format that must be burned into the picture can create a different workload from a compatible text track. Record what the server reports rather than inferring it from the fan noise.
A hypothetical outcome might be direct playback without the track and video transcoding with it. That is evidence of a changed processing route, not yet proof of insufficient hardware. Keep the client version and subtitle format with the result so support can assess compatibility.
Choose an appropriate supported alternative
Where the library legitimately offers another suitable subtitle track, compare that track with the same passage. Preserve the viewer’s language and accessibility needs; a technically easier track that omits necessary information is not automatically an adequate replacement. Avoid deleting subtitle files to hide the problem.
Report the item’s media information, selected subtitle, client, server version and before-and-after mode. Redact private paths and tokens. This app-specific report helps separate subtitle processing from unrelated Wi-Fi changes without claiming that this guide has benchmarked your server or reproduced the buffering.