Will your subtitles survive the bright scenes? Check before you ship them.

White subtitles vanish on a bright sky and glare on an HDR TV. Preview your style over five realistic video scenes and get a real WCAG contrast verdict for every one — measured against the actual pixels behind the words.

  • Your text and frames never leave the device
  • Five realistic scenes + your own frame
  • WCAG 4.5:1 verdict per scene, worst cell
  • Copyable CSS + ASS style for your editor

Preview your subtitle style

Two lines is the broadcast maximum — more lines cover too much of the picture.

28 px is a typical subtitle size on a 640 px-wide frame.
HDR peak warns about glare on bright TVs; it does not change the ratio.
2 px
An outline only helps when it contrasts with the picture too.
One direction only — shown in the preview, not credited in the score.
70%
The broadcast standard: a dark box at about 70% opacity.
Start from a preset:

Check against your own frame

Drop a JPG or PNG frame grab here, or browse your files · up to 10 MB · read only by your browser

Previews update live as you change the style. Everything stays on this device. The verdict is the worst sampled cell, not the average.

Privacy you can verify, not just trust

Most contrast checkers ask for two flat colours. This one can't send your frame anywhere: the scenes are drawn on your own device, an uploaded frame is read only by your browser, and the contrast maths runs locally. Your text and images never leave the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no file fetched after load for the check itself. Don't take our word for it:

New cross-origin requests during use: 0
  1. Press F12 to open developer tools, then the Network tab.
  2. Change the subtitle style or upload a frame above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
  3. Extra credit: disconnect your internet after this page loads — checking still works.

How to check subtitle contrast without uploading a frame

Subtitle contrast fails in a specific way: the text is fine on a dark scene and invisible on a bright one, because the background is a moving picture. A flat-colour contrast checker cannot see that — it tests one pair of colours, and the pair that matters is the text against whatever happens to be behind it at that moment. This tool checks the style where it will actually be seen: over video frames.

When you change a control here, your browser:

  1. Draws five realistic scenes — a bright sky, a dark night, a busy street, a near-white snowfield and a sunset — plus any frame you upload, on canvas. No images are fetched; the scenes are procedural.
  2. Samples the real pixels of the band the subtitle sits on — dozens of cells across the frame — and measures the WCAG contrast of your text against every one of them.
  3. Reports the worst cell, not the average, because a viewer loses the words wherever the background is worst. The median is shown too, so you can see whether the whole scene fails or just its bright parts.
  4. Scores the treatment honestly — a background box is composited over the picture at its opacity; an outline is credited only when both legs hold — text against outline and outline against picture — and a useless outline never hurts, because the direct text-against-picture contrast still counts; a drop shadow is shown but never credited, because it separates the text in one direction only.

What makes this previewer different

The tools that top the results for subtitle contrast are either generic colour-pair checkers — two flat colours, no picture at all — or long guides that explain the rules and leave you to guess. The subtitle readability checkers that do exist test timing and reading speed (characters per second, line length) and say nothing about colour. This page is the only free, no-install, in-browser tool we found that previews a subtitle style over realistic video imagery and scores it against the actual pixels behind the text — with the three treatments editors actually use (outline, shadow, background box), an HDR brightness warning for the glare problem viewers are reporting on modern TVs, and a style you can copy straight into your editor as CSS or an ASS line.

When is checking the right choice — and when is it the wrong one?

Checking is right before you export: when you have picked subtitle colours for a video, a short-form clip, a course, or a game, and you want to know whether they survive the brightest scene in it. It is the wrong choice as a substitute for watching the finished video — a style can pass every scene here and still feel wrong in motion, and the scenes here are representative, not your footage. Upload a frame grab from your own brightest and darkest scenes for the check that actually matters.

Honest limitations

Five scenes, not your video

The built-in scenes are representative — bright, dark, mixed, near-white and high-contrast — but they are not your footage. A style that passes here can still fail on a scene you did not test. Upload your own brightest frame for the real verdict.

Worst cell, not a guarantee

The verdict is the worst sampled cell in the subtitle band. That is the honest number for legibility, but it is a screening check on sampled pixels, not a frame-by-frame audit of a whole video.

Contrast is not the whole story

Reading speed, line length, timing and font choice matter as much as contrast. A subtitle can pass 4.5:1 and still be unreadable if it flashes past at 30 characters a second. Check timing with the Reels Subtitle Timing Checker.

Outline scoring is strict on purpose

An outline is credited only when both legs hold — text against outline and outline against picture. A same-colour outline scores 1:1 and fails, which is correct — it is invisible — even though other checkers would credit it. And a useless outline never hurts: white text with a black outline on a dark scene still passes on the direct contrast.

HDR warning is guidance, not a measurement

The HDR mode cannot measure your TV's peak brightness from a web page. It warns when near-white text is used in HDR peak mode, based on the published 203-nit reference-white guidance — the brightness decision is still yours.

It never changes your video

This tool only reports and hands you a style. Apply the style in your editor, export again, and re-check a frame grab here if you change anything.

Frequently asked questions

Do my frames or subtitle text upload anywhere?

No. The scenes are drawn on your own device, an uploaded frame is read only by your browser, and the contrast maths runs locally — your text and images never leave the device, and the only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the previewer.

Why check subtitles against a picture instead of a flat colour?

Because a subtitle sits on a moving picture, not a flat colour. A generic contrast checker can pass a pair that vanishes on a bright sky and fail a pair that reads fine on a dark scene. This previewer samples the real pixels of the band the subtitle sits on — dozens of cells across the frame — and reports the worst cell, because a viewer loses the words wherever the background is worst, not where it is average.

What do PASS, CAUTION and FAIL mean?

They follow the WCAG 2.2 text thresholds, applied to the worst sampled cell of the scene. PASS means the worst cell is at least 4.5:1 — the AA bar for normal text. CAUTION means it clears 3:1, the large-text bar, but not 4.5:1, so it is marginal at normal subtitle sizes. FAIL means the worst cell is under 3:1 and the text blends into the picture on that scene. The overall verdict is the worst scene's verdict.

What is the broadcast-standard subtitle style?

White text, a 2-pixel black outline and a semi-transparent black background box at about 70% opacity. It is the treatment broadcasters and the Section 508 guidance use because the box guarantees the text sits on a known dark background whatever the scene does. The "Apply broadcast fix" button on this page sets exactly that style, and it passes on every built-in scene.

Why does a white outline around white text still fail here?

Because an outline only helps when it separates the glyph from the picture, and that takes both contrasts holding: text against the outline, and outline against the scene. A white outline around white text scores 1:1 — it is invisible — so neither the direct contrast nor the outline path helps. A black outline around the same white text passes on a white scene, because the black halo defines the letters; and on a dark scene the same style passes on the direct contrast, because the outline simply disappears into the dark. This checker scores it that way on purpose, rather than crediting an outline that does nothing.

Why is a drop shadow not counted in the score?

A drop shadow separates the text in one direction only — usually down and to the right — so it cannot guarantee legibility on a bright or busy background. Crediting it would let a style pass that still fails on the side the shadow does not cover. You can still turn a shadow on and see it in the previews; the score simply does not rely on it, and the fixes list says so when a shadow is the only treatment.

What is the HDR brightness warning about?

On HDR televisions and OLED or mini-LED displays, players draw white subtitles at the display's peak brightness — up to 1,000 to 1,600 nits — instead of the 203-nit reference white that HDR production guidance (ITU-R BT.2408) expects for subtitles. Viewers report that as glare and eye strain in dark rooms, plus blooming around the letters. The contrast ratio still passes, so this is a brightness problem, not a contrast problem. The fix is light grey text instead of pure white, or a smaller size.

Can I use the checked style in my video editor?

Yes. Below the results there is a copyable CSS snippet for web players and captions, and an ASS style line for editors that burn subtitles in with ffmpeg and libass (BorderStyle 3 is the opaque-box style, BorderStyle 1 is outline plus shadow). Paste the style into your editor, export, and re-check a frame grab here if you change anything.

Is there a file size or daily limit?

There is no daily limit and no account. Uploaded frames are capped at 10 MB because they are decoded in the browser, and the five built-in scenes need no file at all. Subtitle text is capped at two lines, because subtitles should never run longer than that — more lines cover too much of the picture.