MAJORFailure Reference

OpenAI Sora Text Rendering Failure — Refund Guide

Technical Classification

OCR-Coupled Token Drift

OCR-Coupled Token Drift on Sora occurs when the model attempts to render explicit text from the prompt but the diffusion process collapses character-level detail. Sora treats text as a visual texture rather than a string, so prompt tokens for "OPEN" can render as "OPLN" or "OPΣN" with character drift increasing on letters wider than 4 chars. Most common on signage, book covers, and screens shown in the foreground.

How to identify this failure

✕Words missing or duplicating letters (e.g. "COFFEE" → "COFFFE")
✕Mixed Latin / non-Latin glyphs in a single word
✕Letter shapes morph mid-clip
✕Numbers swapped (e.g. "Exit 12" → "Exit 1Z")
✕Sign content readable in early frames, unreadable by 0:03

Real generation examples

Prompt used

"A neon sign that reads OPEN 24 HOURS in a rainy street"

Failure observed @ 0:01 → 0:05

Sign reads "OPLN 24 HOLRS" — characters drift after first frame

Prompt used

"Book cover with the title The Great Gatsby on a wooden desk"

Failure observed @ 0:00 → 0:04

Title renders as "The Greaι Gatsby" with mixed Greek and Latin characters

Documentation strength

If you need to escalate

HIGH — Text rendering is a documented Sora weakness and OpenAI honours refund tickets when failure is shown in a still frame.

AVA is a pre-purchase prevention tool, not a post-purchase recovery tool. Platforms generally do not guarantee credit refunds for output-quality failures; goodwill credits are at each platform's discretion. The strength rating reflects how well-formed your support ticket can be, not a promised outcome.

Prevention + documentation steps

01
Score your prompt before you generate
Run your prompt through AVA's pre-flight scoring against the OCR-Coupled Token Drift pattern. Green light = generate. Yellow/red = rewrite using the suggested fix before you commit credits.
02
Capture Generation ID + timestamp if it failed anyway
Find the Generation ID in the URL or share link. Note the exact time when the OCR-Coupled Token Drift first appears (e.g. "failure first visible at 1.2s"). Timestamped evidence is significantly stronger than a general complaint.
03
Use the correct technical term in your support ticket
Describe this failure as "OCR-Coupled Token Drift". This term maps to a recognised internal workflow in the support system and routes the ticket to the right team.
04
Submit via the correct support channel
Runway has no direct email intake. Pro+ plan: open the in-app AI Assistant (help widget bottom-right of app.runwayml.com), describe the failure with the technical term, attach evidence. Free/Standard plan: human support isn't available — your channel is Discord #community-help with @On Call - Moderators.

Frequently asked questions

Does OpenAI refund Sora credits for unreadable text?

Yes — submit a support response ticket citing "OCR-Coupled Token Drift" with the generation ID and a still frame. OpenAI support typically credits within 48 hours.

Why does Sora struggle to render readable text?

Sora has no explicit OCR head — text is rendered as visual texture through the same diffusion process that paints faces and clouds. Strings longer than 4 characters drift because per-character supervision is sparse in the training data.

How can I get Sora to render text correctly?

Use short strings (≤ 4 chars), keep text in the centre of frame, and avoid backgrounds with high visual entropy. AVA flags text-heavy prompts before generation.

Score your prompt

Score your prompt against this failure mode in 30 seconds

Paste your prompt and the platform you intend to use. AVA returns a red/yellow/green score against this specific failure mode plus a concrete rewrite if the risk is high.

Install free All 105 failure modes

AVA Pro · founders' round

$50 for 6 months of unlimited scoring across all failure modes + personal failure-history dashboard. Locks in $13/mo grandfathered after.

Claim $50 founders