No filming:An AI avatar or clone yourself
    Guides

    All-caps captions fail reading speed

    All-caps is slower to parse and taller in the box. Hook posts abuse it. Ads and SDH should stay in sentence case so the mute pass can finish.

    Versely Team••6 min read

    All-caps captions fail reading speed. They are slower to parse and taller in the box. Hook posts use them because they look like a poster. Ads and SDH should not. Sentence case is the mute-pass default. Emphasis is one highlighted word, not a paragraph in caps.

    Word shape is the speed

    Readers do not spell every letter. They recognise the shape of a word. Sentence case keeps that shape: a capital to mark the start, descenders and ascenders to tell “going” from “GOING.” Full caps flatten the silhouette. Every word becomes a rectangle. The eye has to go slower to tell them apart. That delay is characters per second you no longer have.

    Reading speed is already the tight constraint on short-form. Speech outruns comfortable reading. A 1:1 timed cue in sentence case can be finishable. The same cue in caps is the same character count and a harder object. You did not add emphasis. You added friction.

    Height is the second tax. Capitals sit at the full em. A two-line block in caps occupies more vertical space than the same two lines in sentence case. On 9:16 that extra height collides with mouths, with product, and with platform chrome. A “louder” caption is often just a taller caption sitting in the username.

    Line length lies in caps too. A 42-character guideline assumes mixed case. All-caps strings are optically denser. What looked like one line in the transcript wraps in the burn. The wrap is a third line by another name, and three lines lose to TikTok and Reels UI.

    Names and SKUs suffer first. “Siobhán” in caps is harder to check in a QC pass. “XJ-240” in caps next to a sentence in caps is how a model number disappears into shouting. ASR already misses those strings. Caps hide the miss from the person who was supposed to catch it.

    Hook posts abuse it; ads should not

    Organic hook culture treated caps as volume: the first line a poster, the rest a whisper. That is a thumbnail habit dropped onto a timed transcript. A thumbnail is one frame. A caption track is every clause. Shouting every clause is not a hook. It is a tone that does not stop.

    If the spoken hook is three words, you can emphasise those words without capitalising the file. Word-highlight (Snap, Reveal; VEED DYNAMIC) already pops the live token. A second emphasis system — full caps — is redundant and slower. Pick one. The highlight is the karaoke object. Caps are a poster.

    Paid social is a review surface. ALL CAPS next to a price, a health claim, or a legal row reads as unreviewed and as yelling. It also fights the disclosure for height in the same band. BASIC two-line sentence case (simple, plain, corpo) is the ad burn. 21 looks at 1×. None of them require caps to be “on brand.” Brand can live in colour, in a stroke, in a card — not in a paragraph of capitals.

    SDH convention is mixed case, speaker IDs, labelled sounds. Caps for a full cue are not emphasis; they are shouting a deaf viewer cannot turn down. Reserve caps, if you use them at all, for a short ID (JORDAN:) and even then a small label in sentence case is cleaner. Do not set the dialogue in caps “for accessibility.” Accessibility is contrast, time, and clear words — not volume as type.

    Courses and webinar clips inherit the ad/SDH rule. Someone will watch for more than two seconds. Caps for twelve minutes is fatigue. Sentence case holds.

    What to do instead of shouting

    Emphasis, in order:

    1. Cut the sentence. A shorter line is louder than a capitalised long one.
    2. Split the cue. Two finishable blocks beat one poster.
    3. Highlight one word. Karaoke type, or a single accent, on the verb or the number.
    4. Hold the last word a beat after the mouth stops.

    If those four do not get the hook to land, the problem is the script or the plate, not the case. Going to caps is how teams hide a dense offer.

    Contrast is a different knob. White caps on a bright plate still fail. Outline or a backdrop. WCAG contrast is a ratio against the pixels behind the glyphs. Caps do not raise that ratio. They raise the box.

    Placement is a different knob. Caps that sit in the bottom chrome are still covered. Safe area does not expand because the letters are taller. It shrinks, because you used more of it.

    Do not mix caps with emoji on a tight line. Both spend parse time. Both spend width. Paid and SDH skip both. Organic may keep one emoji or a short caps hook, not both on a maxed CPS cue.

    The mute pass, in sentence case

    Lock the cut. Transcribe in the spoken language (165 codes on the VEED path). Fix names and numbers. Leave the transcript in sentence case unless a tiny ID needs a label. Burn BASIC for ads, courses, SDH-ish shorts; DYNAMIC only if the organic hook is a spoken phrase you can still finish. Then watch on mute, on a phone.

    If you cannot finish a line, do not capitalise it. Split, cut, or hold. If a three-word hook still feels quiet in sentence case, try word-highlight on those three words. If it still feels quiet, the words are quiet.

    The AI caption generator and add captions to a video will burn the case you give them. 21 BASIC at 1×, 9 DYNAMIC at 2×. Neither tier is a caps filter. Caption Studio’s Hype and Headline groups are display faces; they are still the wrong object for a full speech track in capitals. Headline is a title row. Speech is a transcript.

    Hook posts will keep shouting in the feed. That is not a reason to ship ads and SDH that way, and it is not a reason to fail CPS on an organic cut you could have saved with sentence case and a split.

    Set the next track in sentence case in Versely.

    FAQ

    Are a few words in caps on the hook allowed?

    A short hook can take emphasis. Full-cue caps on every line fail reading speed. Prefer word-highlight or one accented word. Ads and SDH should stay in sentence case.

    Does all-caps help accessibility?

    No. It slows parsing, tallens the block, and collides with chrome. Accessibility is contrast, time on screen, and accurate words — including speaker IDs and labelled sounds for SDH — not shouting.

    Will a condensed caps font fix the height problem?

    It trades height for density. The eye still loses word shape, and a condensed line is easier to overflow. Sentence case in a readable face, two lines, mute pass. That is the fix.