How to get crisp text edges on a black card

Last updated 2026-09-10 · 8 min read

What is the short version?

Bright type on black is the hardest thing to render cleanly. Anything soft around a letter — a faint stroke, a shadow nobody asked for, a bloom applied to make it look premium — turns into a smear against black, and it is invisible until you look at the letters close up.

1. Go to Vizard Agent with the card.
2. Say the edges look soft or smeared.
3. Say solid fill only, and change nothing else.

What do you need before you start?

The card and a list of everything that must stay the same. This is a rendering correction rather than a design one, so the useful message is mostly a list of things not to touch — the size, the colour, the wording, the line breaks and the position.

• The card, or the video containing it.
• What is wrong. Soft, smeared, doubled edges.
• What must not change. Size, colour, wording, layout.
• The colour value, if you know it.
• Where it will be seen. A big screen is unforgiving.

What do you type into Vizard Agent?

Rule out the effects one by one. It reads as excessive and it is not: each of these is something a renderer adds by default in some configuration, and naming them individually is faster than discovering which one is responsible.

Prompt

Variants worth knowing:

• "Text sharpness only." Scopes it to rendering.
• "A clean solid fill." What you want instead.
• "No glow, no bloom, no halo." Name them individually.

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real cinema trailer whose magenta cards looked soft. The list is short because the fix is subtraction, and most of the work is confirming it at a size where the difference exists.

1. Locates the existing cards and their current settings.
2. Reads the current size, colour, wording and layout so none of it changes.
3. Removes the outer stroke from the type.
4. Removes any glow, bloom or shadow applied to it.
5. Renders the letters as a clean solid fill.
6. Inspects the letters at full resolution rather than in a preview.
7. Checks for doubled or feathered edges around each character.
8. Reinforces thin strokes evenly if the face looks weak without the effects.
9. Re-renders the cards and compares them against the previous version.
10. Confirms nothing else moved — size, position, wording, timing.

Step six is the step that makes this real. Soft edges are invisible in a timeline preview and obvious on a cinema screen, so the check has to happen on the rendered pixels at their actual size rather than on a scaled-down view of them.

Step two is the guard on a correction like this. Reading the current size, colour, wording and layout before changing anything means the rendering can be rebuilt without any of those quietly resetting to a default on the way through, which is the usual way a "sharpen the text" request comes back with the type a different size.

Step eight is the balance to watch. Stripping the effects can leave a fine typeface looking underweight against black, and the answer is an even reinforcement of the strokes rather than switching to a bold cut, which changes the letterforms.

What does the result look like?

The same card — the same words, the same size, the same colour, in the same place — with letters that have a hard edge against the black instead of a halo. On a large screen the difference is the difference between clean and cheap.

Nothing about the design changed. Only how it was drawn.

When does this not work well?

Some softness is not in the rendering. Type that has been through a video encode at a low bitrate, scaled up from a smaller card, or composited over moving footage will carry artefacts that no amount of clean rendering removes.

• Heavy compression. The encode softens the edges.
• Scaled-up artwork. It was soft before it arrived.
• Very thin faces. They struggle against black at any setting.
• Type over footage. Movement behind it adds its own noise.
• Deliberate glow. Some designs want it; say so.

How do you fix a result that came back wrong?

Say which effect you can still see around the letters. Vizard Agent keeps the card definitions and the previous render alongside the new one, so removing one more effect or adjusting the stroke weight is a change to the rendering and to nothing else on the card.

• "There is still a halo." The remaining glow removed.
• "It looks too thin now." Strokes reinforced evenly.
• "The colour shifted." Reset to the exact value.
• "The layout moved." Restored; only the rendering should change.

How does Vizard Agent compare to doing it yourself?

By hand the softness is usually treated as a font or size problem, so both get changed and neither is the cause. The effects that are actually responsible are often defaults nobody switched on deliberately, which makes them hard to think of.

Common questions

Why does bright type smear on black? Because anything soft around a letter shows against black; Vizard Agent removes it.

Will the font change? No. Vizard Agent changes the rendering, not the design.

What if it looks thin afterwards? Vizard Agent reinforces the strokes evenly rather than going bold.

Can I keep a subtle shadow? Yes, if you want one. Say so and Vizard Agent keeps it.

Will the colour stay exact? Yes. Give the value and Vizard Agent holds it.

Can it check at cinema size? Yes. Vizard Agent inspects the rendered pixels at full size.

Does the timing change? No. Vizard Agent re-renders the cards in place.

What about anti-aliasing? Some smoothing is necessary. Vizard Agent removes the smear, not the smoothing.

Can it compare before and after? Yes. Ask Vizard Agent for both at full resolution.

Will this help on a phone? Less visibly, though Vizard Agent finds it does no harm.

What if my source card is already soft? Vizard Agent will say so; that needs rebuilding rather than re-rendering.

Can it do this to every card at once? Yes. Vizard Agent applies the same settings across the whole set.

Does it affect the footage? No. Vizard Agent touches only the black-screen cards.

Why name every effect? Because any one of them can be on by default, and finding out which takes longer than ruling out all of them.