{"id":58761,"date":"2026-11-17T08:55:06","date_gmt":"2026-11-17T07:55:06","guid":{"rendered":"https:\/\/nzbusenet.com\/strange-characters-in-your-subtitles-heres-how-to-save-an-srt-file-correctly\/"},"modified":"2026-11-17T08:55:12","modified_gmt":"2026-11-17T07:55:12","slug":"strange-characters-in-your-subtitles-heres-how-to-save-an-srt-file-correctly","status":"publish","type":"post","link":"https:\/\/nzbusenet.com\/en\/strange-characters-in-your-subtitles-heres-how-to-save-an-srt-file-correctly\/","title":{"rendered":"Strange characters in your subtitles? Here\u2019s how to save an SRT file as UTF-8"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Strange characters in your subtitles? Does your subtitle suddenly show \u2018caf\u00c3\u00a9\u2019 instead of \u2018caf\u00e9\u2019? Or do you see a question mark where the \u2018\u00eb\u2019 should be in \u2018Belgi\u00eb\u2019? If so, there is likely an issue with the character encoding. You can often fix this by opening the SRT file using the correct encoding and then saving it as UTF-8.<\/p>\n\n<p class=\"wp-block-paragraph\">Before saving, check that the text is clearly legible. If you see \u2018caf\u00c3\u00a9\u2019 and save the file directly as UTF-8, you might end up permanently saving the incorrect text. Read on to learn how to prevent this.<\/p>\n\n<h2 class=\"wp-block-heading\">Why are there strange characters in my subtitles?<\/h2>\n\n<p class=\"wp-block-paragraph\">An SRT file contains subtitle text, line numbers, and timecodes. Character encoding determines how a program converts the bytes in that file into letters and punctuation marks. Many SRT files use UTF-8. In older files, you may encounter other encodings, such as Windows-1252 for Western European text.<\/p>\n\n<p class=\"wp-block-paragraph\">Standard letters like &#8216;a&#8217; and &#8216;e&#8217; may still display correctly even with incorrect encoding. The problem often only becomes apparent with accented characters, the euro symbol, or typographic quotation marks. Sometimes, the characters themselves provide a clue as to where you should begin.<\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>What you see<\/th><th>What you can check<\/th><\/tr><\/thead><tbody><tr><td>or<\/td><td>Try opening the original file using UTF-8 encoding. This pattern often occurs when a UTF-8 file is read as Windows-1252.<\/td><\/tr><tr><td>or<\/td><td>For older Dutch subtitles, try using Windows-1252 encoding. A replacement character may appear if the chosen encoding cannot interpret the original bytes.<\/td><\/tr><tr><td>An empty square appears on the TV, while the same text displays correctly on your PC<\/td><td>Check whether your TV is using the same subtitle file. If it is, the font being used might be missing a specific character.<\/td><\/tr><tr><td>, including in the original download<\/td><td>The question mark might already be present in the file. If necessary, find a different subtitle or correct the words in question manually.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\">First, make a copy of the original SRT file. This allows you to start over if you happen to choose the wrong encoding.<\/p>\n\n<h2 class=\"wp-block-heading\">Saving an SRT file as UTF-8 using Notepad<\/h2>\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"859\" height=\"151\" src=\"https:\/\/nzbusenet.com\/wp-content\/uploads\/2026\/11\/afbeelding.png\" alt=\"Saving an SRT file as UTF-8 using Notepad &#x2013; Strange characters in your subtitles\" class=\"wp-image-58756\" title=\"\" srcset=\"https:\/\/nzbusenet.com\/wp-content\/uploads\/2026\/11\/afbeelding.png 859w, https:\/\/nzbusenet.com\/wp-content\/uploads\/2026\/11\/afbeelding-250x44.png 250w\" sizes=\"auto, (max-width: 859px) 100vw, 859px\" \/><\/figure>\n\n<p class=\"wp-block-paragraph\">This method is useful if the text in Notepad is already clearly readable and you want to save a new copy as UTF-8.<\/p>\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li>Right-click the SRT file and select Open with \u2192 Notepad.<\/li>\n\n\n\n<li>Look for a few lines containing words such as \u2018caf\u00e9\u2019, \u2018\u00e9\u00e9n\u2019, or \u2018Belgi\u00eb\u2019. Also, check for quotation marks and any other accented characters.<\/li>\n\n\n\n<li>Select File \u2192 Save as.<\/li>\n\n\n\n<li>Under \u2018Save as type\u2019, choose \u2018All files\u2019 and give the copy a name (for example, by adding a suffix to the original filename).<\/li>\n\n\n\n<li>Select \u2018UTF-8\u2019 as the encoding and save the file.<\/li>\n\n\n\n<li>Open the new SRT file and check those same lines again.<\/li>\n<\/ol>\n\n<p class=\"wp-block-paragraph\"><code>.srt.txt<\/code>Do you see any strange characters appearing at step 2? If so, try opening the original file again using a different source encoding. Subtitle Edit allows you to better observe the results as you test various settings. If you are unable to load the new file, check whether Windows has altered it in some way without your knowledge.<\/p>\n\n<h2 class=\"wp-block-heading\">Verkeerd weergegeven tekens herstellen met Subtitle Edit<\/h2>\n\n<p class=\"wp-block-paragraph\">Open the original SRT file in Subtitle Edit. If the text appears incorrectly, use the option to open or import a subtitle file with a manually selected encoding. The name and location of this option may vary depending on the version.<\/p>\n\n<p class=\"wp-block-paragraph\">Try UTF-8 first if you see combinations like [\u2026]. If you encounter many replacement characters\u2014such as [\u2026].\u2014in an older Dutch file, try Windows-1252 instead. Check several lines throughout the file; a single word might look correct, while quotation marks or other accented characters could still be displayed incorrectly.<\/p>\n\n<p class=\"wp-block-paragraph\">Once the text is correct, select <strong>SubRip (.srt)<\/strong> as the format and <strong>UTF-8<\/strong> as the encoding when saving. Use &#8220;<strong>Save As&#8221;<\/strong> to create a new copy. Changing the encoding does not require any adjustments to the timecodes. If the text displays correctly on screen after saving, but appears too early or too late, follow the guide on <a href=\"https:\/\/nzbusenet.com\/en\/adjusting-subtitle-timing-with-subtitle-edit-and-saving-permanently\/\">adjusting subtitle timing using Subtitle Edit<\/a>.<\/p>\n\n<h2 class=\"wp-block-heading\">Test your repaired subtitles in VLC or on your TV.<\/h2>\n\n<p class=\"wp-block-paragraph\">Open the video and manually select the new SRT file. This ensures that you are testing the modified version\u2014especially important if the video also contains embedded subtitle tracks. Would you like your player to detect the external subtitle file automatically? Place both files in the same folder and give them the same base filename (for example, `movie.mp4` and `movie.srt`).<\/p>\n\n<p class=\"wp-block-paragraph\">Are the characters displayed incorrectly only in VLC? Check the default subtitle encoding under Tools \u2192 Preferences \u2192 Subtitles\/OSD. You can test whether a different setting resolves the issue; this setting applies specifically to VLC. You can also try using the same subtitle file\u2014ensuring it is correctly saved in UTF-8 format\u2014on other devices. VLC documentation on incorrectly displayed charactersZijn de tekens alleen in VLC verkeerd? Controleer onder <strong>Extra \u2192 Voorkeuren \u2192 Ondertitels\/OSD<\/strong> de standaardcodering voor ondertitels. Je kunt daar testen of een andere instelling het probleem oplost. Die instelling geldt voor VLC. Met een correct opgeslagen UTF-8-bestand kun je dezelfde ondertitel ook op andere apparaten proberen. <a href=\"https:\/\/docs.videolan.me\/vlc-user\/en\/support\/faq\/faqwindows.html\" rel=\"nofollow noopener\" target=\"_blank\">VLC-documentatie over verkeerd weergegeven tekens<\/a><\/p>\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions: Strange characters in your subtitles?<\/h2>\n\n<p class=\"wp-block-paragraph\">Below is a list of frequently asked questions regarding strange characters in your subtitles.<\/p>\n\n<h3 class=\"wp-block-heading\">What is the difference between UTF-8 and UTF-8 with BOM?<\/h3>\n\n<p class=\"wp-block-paragraph\">A BOM is a short marker at the beginning of a file that helps some programs recognize UTF-8. Start by using UTF-8 without a BOM. If you have an older player that misidentifies the encoding, try creating a separate copy that includes a BOM and see which version your player displays correctly.<\/p>\n\n<h3 class=\"wp-block-heading\">Is it always possible to fix subtitles that contain question marks?<\/h3>\n\n<p class=\"wp-block-paragraph\">That depends on where the question marks appear. If they only show up in your media player, the original file might still contain all the correct characters. If the characters in the original file have already been replaced by question marks, then the SRT file no longer holds any information about what those original characters were. You can either correct the words yourself or look for a different version of the subtitle on one of these <a href=\"https:\/\/nzbusenet.com\/subtitle-download-sites-download-srt-files\/\">download subtitles websites<\/a>.<\/p>\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<div class=\"mh-excerpt\"><p>Strange characters in your subtitles? Does your subtitle suddenly show \u2018caf\u00c3\u00a9\u2019 instead of \u2018caf\u00e9\u2019? Or do you see a question mark where the \u2018\u00eb\u2019 should be in \u2018Belgi\u00eb\u2019? If so, there is likely an issue <a class=\"mh-excerpt-more\" href=\"https:\/\/nzbusenet.com\/en\/strange-characters-in-your-subtitles-heres-how-to-save-an-srt-file-correctly\/\" title=\"Strange characters in your subtitles? Here\u2019s how to save an SRT file as UTF-8\">[&#8230;]<\/a><\/p>\n<\/div>","protected":false},"author":12223,"featured_media":58762,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[1180],"tags":[],"class_list":["post-58761","post","type-post","status-publish","format-standard","has-post-thumbnail","category-edit-subtitels"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/nzbusenet.com\/wp-content\/uploads\/2026\/11\/Rare-tekens-in-je-ondertiteling.png","_links":{"self":[{"href":"https:\/\/nzbusenet.com\/en\/wp-json\/wp\/v2\/posts\/58761","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nzbusenet.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nzbusenet.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nzbusenet.com\/en\/wp-json\/wp\/v2\/users\/12223"}],"replies":[{"embeddable":true,"href":"https:\/\/nzbusenet.com\/en\/wp-json\/wp\/v2\/comments?post=58761"}],"version-history":[{"count":1,"href":"https:\/\/nzbusenet.com\/en\/wp-json\/wp\/v2\/posts\/58761\/revisions"}],"predecessor-version":[{"id":58763,"href":"https:\/\/nzbusenet.com\/en\/wp-json\/wp\/v2\/posts\/58761\/revisions\/58763"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nzbusenet.com\/en\/wp-json\/wp\/v2\/media\/58762"}],"wp:attachment":[{"href":"https:\/\/nzbusenet.com\/en\/wp-json\/wp\/v2\/media?parent=58761"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nzbusenet.com\/en\/wp-json\/wp\/v2\/categories?post=58761"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nzbusenet.com\/en\/wp-json\/wp\/v2\/tags?post=58761"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}