Emby Emby Emby Learn
  • Emby Home
  • Video
  • Audio
  • Media Files
    • Subtitles and captions
    • Photos and images
    • Metadata and discovery
    • Libraries and media collections
    • Playback and streaming
    • Media hardware acceleration
    • Displays and AV connections
    • Live TV and recording
  1. Emby Learn
  2. Subtitles and captions
  3. Subtitle sources
  4. Finding subtitle sources
Search Results for

    Show / Hide Table of Contents

    Finding subtitle sources

    Subtitle sources provide caption content through existing media, external releases, providers or authored recognition/translation, with distinct matching and provenance questions.

    A usable subtitle begins with the right content for the programme and viewer. Its format and delivery matter afterward. A file can be valid SRT and still be the wrong edit, language, translation or accessibility role.

    Source What needs checking
    Existing media track or caption service Intended track/service, timing, styles and resources
    External release file Edition, language, role and integrity
    Subtitle provider Candidate identity, release match and successful download
    Human-authored transcript/translation Content accuracy, timing and presentation
    Speech recognition output Recognized wording, alignment and caption authoring
    Automated translation Meaning/context, retained timing and readable layout

    Those sources can produce similar filenames while having different provenance.

    Match the programme before changing timing

    Title/year or episode identity is an initial search key. It does not establish an exact cut. Release details, duration and a provider's supported file fingerprint can strengthen the match.

    Compare recognizable lines near the beginning, middle and end. A fixed difference suggests an offset; progressive change or a scene-boundary step suggests other relationships. Release matching considers those candidate clues without replacing the timing analysis.

    A subtitle already inside the matching media can provide useful timing evidence, but selecting another language or role still changes the content. An extracted dialogue track does not become SDH because it was found locally.

    Retain the content's role and provenance

    A sparse forced-passage track and a complete dialogue translation can both be English. A transcript with speaker/sound descriptions serves another need from plain spoken-word text.

    Provider metadata, filenames and authored records can describe those distinctions. The actual wording establishes whether they are present. Keeping the source description helps explain why two candidates differ.

    For Emby, manual and automatic downloads cover the configured provider workflows; external naming covers identification. These instructions are separate from judging which candidate fits the edition being played.

    Generated content needs its own review

    Speech recognition estimates spoken words from audio. Translation expresses meaning in another language. Neither inherently reconstructs a full accessible caption presentation, and both can need content and timing work.

    Extraction from a caption service instead interprets coded content already present in the source. OCR recognizes pictured letters. Choosing the appropriate operation avoids asking a simple extraction tool to recover information its input never contained.

    See Also

    • Subtitle release matching
    • OpenSubtitles
    • Automatic speech recognition for captions
    • Subtitle translation
    • Subtitle extraction

    References

    • Matroska subtitle mappings
    • W3C WAI: Captions and subtitles
    • OpenSubtitles: OSHash algorithm reference
    • W3C WebVTT, May 2026 Candidate Recommendation Draft
    On this Page
    2026 © EMBY LLC. Please see our terms of use and privacy policy.
    Back to Top