How do I batch embed Turkish SRT subtitles into matching video files without breaking special characters?

Short Answer

In short, yes, you can batch embed matching Turkish SRT files into videos, but the key is to separate three issues: filename matching, subtitle text encoding, and container/player support. Turkish characters such as ş, ğ, ü, İ, and ı usually fail because the SRT is read as the wrong legacy code page, not because subtitles are impossible to embed. Use MKV for the cleanest soft-subtitle workflow, convert or declare the subtitle encoding, and verify a few outputs before running the whole folder; the detailed breakdown below gives a safer repeatable process.

AI tools are useful for sketching the batch logic, but they are weak at diagnosing character encoding unless you give them exact sample bytes, your OS, the player, and the command output. Treat the script as an automation wrapper around FFmpeg, not as the source of truth. FFmpeg, Matroska, and encoding documentation are the parts to trust when deciding the final command.

What Is Probably Going Wrong

An SRT file is plain text with subtitle numbers, timestamps, and caption text. The awkward part is that SRT files do not always carry a reliable encoding declaration. A Turkish subtitle file made on Windows may be saved as Windows-1254, ISO-8859-9, UTF-8 with BOM, or UTF-8 without BOM. If FFmpeg or PowerShell guesses wrong, the video may mux successfully while characters render as mojibake, question marks, or missing glyphs.

For MKV output, Matroska’s subtitle mapping expects SRT text to be stored as UTF-8. That means your goal is not merely to attach the .srt file; your goal is to ensure FFmpeg receives the subtitle text with the correct character interpretation before it writes the Matroska subtitle stream. You can do that by converting every SRT to UTF-8 first, or by telling FFmpeg the input subtitle character encoding with the correct option when decoding the subtitle file.

Also check the difference between soft subtitles and burned-in captions. Soft subtitles are separate selectable tracks inside the video container. They are better for archives, language tracks, and players where users can turn captions on or off. Burned-in captions are rendered into the pixels of the video, which is usually better for TikTok, Reels, Shorts, and other social posts because platforms and viewers handle visible captions more consistently.

Safer Batch Workflow

For a local archive, use MKV output first. It handles subtitle tracks cleanly, can keep video and audio with stream copy, and avoids MP4 subtitle compatibility surprises. Before a full folder run, test one known-bad Turkish line containing ş, ğ, ü, İ, ı, ö, and ç. If the output looks correct in two players, then scale the batch. If you are turning the same material into short social edits, clean the subtitle source first, then draft the clips in YumCut so the captions and visual pacing can be reviewed before publishing.

A practical FFmpeg shape is: input video, input subtitle, map the original video and optional audio, map the subtitle, copy the video/audio streams, encode or mux the subtitle as a text subtitle track for MKV, and set Turkish language metadata. If the SRT is Windows-1254, put the subtitle character encoding option before the subtitle input, because it applies to decoding that input. Conceptually: `ffmpeg -i video.mp4 -sub_charenc windows-1254 -i video.srt -map 0:v -map 0:a? -map 1:0 -c:v copy -c:a copy -c:s srt -metadata:s:s:0 language=tur output.mkv`.

Be careful with `forced`. A forced subtitle track usually means subtitles that should appear even when the viewer has subtitles off, such as translated signs or a few foreign-language lines. A full Turkish subtitle track should normally be marked default only if you want Turkish to be the default subtitle for that file. Setting both default and forced on every full subtitle track can confuse players and viewers.

Manual Review Still Matters

Run a small QA pass after the script finishes. Use FFprobe or a media player’s track info to confirm the subtitle track exists, the language tag is Turkish, and the file has the expected audio and video streams. Then watch 30-60 seconds around lines with Turkish-specific characters. Encoding failures often show up only in the captions, while the file otherwise looks successful.

If the final destination is social video, soft subtitles inside an MKV are usually not the final deliverable. Most social platforms expect captions to be provided through their own caption tools or burned into the video. In that case, use the SRT as a clean source of truth, create the video in YumCut or your editor with visible caption styling, and export a platform-ready vertical version. Manual review is still needed for line breaks, timing, reading speed, profanity/context, and whether Turkish casing looks right.

The repeatable rule is simple: automate file matching and muxing, but manually inspect encoding and viewer experience. Batch scripts save time only after you have proven the first few outputs are correct.