# Incorrect subtitle rendering

**URL:** <https://forums.plex.tv/t/incorrect-subtitle-rendering/838042>\
**Category:** Plex Media Server\
**Tags:** server-linux, server-docker\
**Created:** [April 15, 2023, 10:26pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042 "2023-04-15T22:26:35Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrys938](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@andrys938](https://forums.plex.tv/u/andrys938)\
**Post date:** [April 15, 2023, 10:26pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/1 "2023-04-15T22:26:35Z")

</div>

Server Version#: 1.32.0.6918

In some .mkv containers, the subtitle font is set to Trebuchet MS. Since this font is missing from the docker container and the Linux build, subtitles are not displayed correctly. (no spaces, small punctuation marks)

```auto
24
00:01:34,720 --> 00:01:38,930
<font face="Trebuchet MS" size="24"><i>A treasure that was too dangerous 
to sell, and too dangerous to use.</i></font>

```

Incorect

 ![incorrectSub](https://global.discourse-cdn.com/plex/original/4X/8/b/b/8bb03d70cd7fb158dbbcef8bb6399b89680b2f52.jpeg)

Correct

 ![correctSub](https://global.discourse-cdn.com/plex/original/4X/8/f/b/8fb110c0ee1593436e17272e1b832be8232269ef.jpeg)

---

<div class="post-metadata">

**Author:** ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)\
**Post date:** [April 15, 2023, 10:40pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/2 "2023-04-15T22:40:25Z")

</div>

The copyright of this font lies with Microsoft. Therefore it is not possible for Plex to include it into its own software. It can only make use of this font if it’s already present in the operating system (which is the case on Windows).  
There is no guarantee whatsoever that Plex will be able to render any random font which somebody has defined in some random subtitle file.

Use a different subtitle or remove the font definition.

---

<div class="post-metadata">

**Author:** ![andrys938](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@andrys938](https://forums.plex.tv/u/andrys938)\
**Post date:** [April 16, 2023, 9:21am UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/3 "2023-04-16T09:21:01Z")

</div>

It seems that in the previous version 1.31.3.6868, Plex ignored the font defined in the subtitles and used a more acceptable default font. (there are spaces, and punctuation marks have a certain size)

 ![1.31.3.6868](https://global.discourse-cdn.com/plex/original/4X/6/8/4/684c96fac68cd24dae581dde9e742c232068b017.jpeg)

It would be great if you could revert to the old default font in case a certain font is unavailable.

---

<div class="post-metadata">

**Author:** ![annonimus84](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@annonimus84](https://forums.plex.tv/u/annonimus84)\
**Post date:** [April 21, 2023, 8:32pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/4 "2023-04-21T20:32:18Z")

</div>

Is there a way to upvote this topic? 🙂  
Many of my videos have the same issue as described above: the whitespaces between words are too narrow making the subtitles unreadable… ☹

---

<div class="post-metadata">

**Author:** ![rozzly](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rozzly](https://forums.plex.tv/u/rozzly)\
**Post date:** [April 22, 2023, 3:55pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/5 "2023-04-22T15:55:22Z")

</div>

Bumping this. I just went through the investigation steps (log collection, screenshots, etc) before seeing this thread. I’m having the exact same issue after upgrading. This impacting the WEB player as well as the Samsung TV player, however subtitles are rendering fine through Roku and the Plex Windows Dekstop App.

**Web App** :

 ![subs2-plex-web-windows](https://global.discourse-cdn.com/plex/original/4X/4/a/d/4adcecc981ea05c189ced70fd6f0ce8ee18d4f1d.jpeg)

**Desktop App** :

 ![subs1-plex-app-windows](https://global.discourse-cdn.com/plex/original/4X/f/9/c/f9c6341997ea818a72440c762646c7d68864ec16.jpeg)

**Subtitle Details** :

`Style: Italics TK,Gandhi Sans,72,&H00FFFFFF,&H000000FF,&H00593435,&H00593435,-1,-1,0,0,100,100,0,0,1,2.3,0.6,2,30,30,60,0`

`Dialogue: 10,0:00:17.70,0:00:21.62,Italics TK,Nasa,0,0,0,,It's like my life is being \Nsucked up by this snow.`

There’s only one Style that uses ‘Trebuchet MS’ and it’s a sign translation; I’m not sure why it would impact the entire output of the file instead of just that section. – **I’m also not an expert on subtitles.**

@OttoKerner

---

<div class="post-metadata">

**Author:** ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)\
**Post date:** [April 22, 2023, 6:19pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/6 "2023-04-22T18:19:41Z")

</div>

It looks more like there is no high-quality font available in your Docker container for the Plex Transcoder to use. So it is falling back to some font with very poor kerning.

---

<div class="post-metadata">

**Author:** ![rozzly](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rozzly](https://forums.plex.tv/u/rozzly)\
**Post date:** [April 22, 2023, 9:10pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/7 "2023-04-22T21:10:09Z")

</div>

If this were based on the container or install, I’d expect more consistency with the output between different players. Eg, I’d expect the font to be messed up while transcoding to the Roku app or Windows Desktop app, but it works fine through those.

---

<div class="post-metadata">

**Author:** ![fearherbs1](https://avatars.discourse-cdn.com/v4/letter/f/ccd318/32.png) [@fearherbs1](https://forums.plex.tv/u/fearherbs1)\
**Post date:** [April 22, 2023, 10:18pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/8 "2023-04-22T22:18:47Z")

</div>

Same issue here. Happens on both my binhex/arch-plexpass docker install as well as my Ubuntu 22.04.2 LTS Install. Reverting back to 1.31.3.6868 solved the issue for me. I am also only having the issue on specific players, notably the web player.

 ![brokensubs](https://global.discourse-cdn.com/plex/original/4X/0/b/7/0b724d4f9f3bc33b7bab9cabd778231c66126b0c.png)

#### Subtitle file in Aegisub:

 ![image](https://global.discourse-cdn.com/plex/original/4X/6/5/6/6568f56ab68912db019e818edb9e70a5ef75b9a6.png)

---

<div class="post-metadata">

**Author:** ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)\
**Post date:** [April 23, 2023, 7:51am UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/9 "2023-04-23T07:51:33Z")

</div>

> [@rozzly](#):
>
> If this were based on the container or install, I’d expect more consistency with the output between different players.

The font file on the server is only used by the Transcoder, if it has to “burn in” subtitles. And that is only necessary if

- it has been requested by the client, due to a client preference (“burn in subtitles”)
- the client cannot render the type of subtitles (PGS/VOBSUB vs. SRT etc )

Subtitle format support varies between different client types. So the issue not being consistent is only logical. The clients which show subtitles correctly, are those which can render the subtitles themselves.

---

<div class="post-metadata">

**Author:** ![rozzly](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rozzly](https://forums.plex.tv/u/rozzly)\
**Post date:** [April 23, 2023, 10:35am UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/10 "2023-04-23T10:35:46Z")

</div>

> [@fearherbs1](#):
>
> Reverting back to 1.31.3.6868

@OttoKerner , It looks like reverting back to 1.31.3.6868 does in fact resolve this issue. Something must have changed – this might have come with the update to deprecate support for older systems?

---

<div class="post-metadata">

**Author:** ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)\
**Post date:** [April 23, 2023, 1:18pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/11 "2023-04-23T13:18:06Z")

</div>

Is someone here using a Synology NAS as server and is experiencing the same issue?

---

<div class="post-metadata">

**Author:** ![rozzly](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rozzly](https://forums.plex.tv/u/rozzly)\
**Post date:** [April 23, 2023, 3:26pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/12 "2023-04-23T15:26:52Z")

</div>

No, but if it’s for the sake of troubleshooting, I can be.

---

<div class="post-metadata">

**Author:** ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)\
**Post date:** [April 23, 2023, 3:29pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/13 "2023-04-23T15:29:29Z")

</div>

I’ve seen at least one report from a Synology user who days it is the same on Synology, but not on Windows.  
Which suggests that all Linux based platform might be affected.

---

<div class="post-metadata">

**Author:** ![rozzly](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rozzly](https://forums.plex.tv/u/rozzly)\
**Post date:** [April 23, 2023, 3:31pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/14 "2023-04-23T15:31:32Z")

</div>

I’m running Plex inside a Proxmox LXC container based on Ubuntu 22.10

Based on my testing, the issue has been client specific:

**Plex Web Client** : Bad formatting  
**Plex Desktop Client** : Good formatting  
**Samsung TV App** : Bad formatting  
**Roku Stick TV App** : Good formatting

---

<div class="post-metadata">

**Author:** ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)\
**Post date:** [April 23, 2023, 3:32pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/15 "2023-04-23T15:32:14Z")

</div>

I’ve explained above why that might be.

---

<div class="post-metadata">

**Author:** ![rozzly](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rozzly](https://forums.plex.tv/u/rozzly)\
**Post date:** [April 23, 2023, 3:37pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/16 "2023-04-23T15:37:36Z")

</div>

Right, I can confirm the Plex Desktop Client direct streams the subtitles while the web client burns them – makes sense. If you need any kind of testing done, just let me know.

---

<div class="post-metadata">

**Author:** ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)\
**Post date:** [April 23, 2023, 3:42pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/17 "2023-04-23T15:42:32Z")

</div>

So, my working hypothesis so far is that this is affecting text-based subtitle formats (SRT, ASS) which are getting burned-in on the server.  
Which means that if you are using the web app, you can only reproduce it with ASS subs, because the web app can render SRT subs itself.

Picture-based subs are not affected, because they don’t need a font. They are simply bitmap pictures.

---

<div class="post-metadata">

**Author:** ![Kwakx11](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/kwakx11/32/205236_2.png) [@Kwakx11](https://forums.plex.tv/u/Kwakx11)\
**Post date:** [April 23, 2023, 8:11pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/19 "2023-04-23T20:11:24Z")

</div>

Same problem here, 1.32.1.6983 running in docker (official plexinc/pms-docker image) on UnRAID.

 ![image](https://global.discourse-cdn.com/plex/original/4X/0/b/5/0b59e1403f01c582c4ead61704a70a4f3f6144e7.jpeg)

---

<div class="post-metadata">

**Author:** ![fearherbs1](https://avatars.discourse-cdn.com/v4/letter/f/ccd318/32.png) [@fearherbs1](https://forums.plex.tv/u/fearherbs1)\
**Post date:** [April 23, 2023, 8:11pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/20 "2023-04-23T20:11:32Z")

</div>

Was able to do a bit more testing today, It seems to be definitely only when the subs are burned in. As switching my plex web player settings to “Only Image Formats”:

 ![image](https://global.discourse-cdn.com/plex/original/4X/9/f/8/9f83dd4afbe0624af2b9d02031442072e1660bde.png)

Results in the subtitles showing without issue:

 ![image](https://global.discourse-cdn.com/plex/original/4X/3/0/a/30a7825010f98448ea7458e75278f2484fe9b428.jpeg)

However this seems to have the side effect of causing playback failures and rendering issues for more complex subtitles that worked fine with the “automatic” burn in setting:

### The following plays for a few seconds before crashing and seems to have the wrong font applied:

 ![image](https://global.discourse-cdn.com/plex/original/4X/b/a/0/ba07a145f7ed251860da8ccd8c498b5ab69bbc17.jpeg)

 ![image](https://global.discourse-cdn.com/plex/original/4X/c/7/e/c7ec70baa3138220d93bcbef789d146a12d66d43.png)

When it looks fine and plays back perfectly fine with the burn in set to “Automatic”:

 ![image](https://global.discourse-cdn.com/plex/original/4X/9/7/f/97f91161a6b3a78f6379156514f75cd9e6a549f2.png)

 ![image](https://global.discourse-cdn.com/plex/original/4X/3/4/e/34e369a29c17cb4e65f6ee40ab85674a06d112cb.jpeg)

I can also do any more testing if needed

---

<div class="post-metadata">

**Author:** ![Kwakx11](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/kwakx11/32/205236_2.png) [@Kwakx11](https://forums.plex.tv/u/Kwakx11)\
**Post date:** [April 23, 2023, 8:24pm UTC](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042/21 "2023-04-23T20:24:15Z")

</div>

Thank you, it works for me as temporary fix. I set to “never” on my LG TV app and it helps there too.

[Next page](https://forums.plex.tv/t/incorrect-subtitle-rendering/838042.md?page=2)
