
YouTube requires a video to be at least 25 seconds long before it can have an end screen. End-screen elements belong within the final 5–20 seconds. A shorter AI teaser may therefore be ineligible even if its last frame already contains a drawn recommendation button. That graphic is not the platform's clickable element.
Key Takeaways
- Confirm the exported runtime before designing around an end screen.
- Reserve picture space and timing for real interactive elements.
- Viewer context can hide or change an otherwise valid end screen.
Separate eligibility from the artwork
The official YouTube end-screen guide states the duration requirement and placement window. It also excludes made-for-kids videos and certain viewing contexts. Do not change the video's audience classification merely to unlock a feature.
Measure the actual uploaded cut. A twenty-second teaser does not become eligible because its editing project contains an unused longer sequence. Decide whether a genuinely useful longer edit is appropriate or whether the short film should use another suitable navigation route. Adding empty footage solely to satisfy a control can weaken the film.
Protect the ending before placing elements
Inspect the final scene for faces, story resolution, captions and essential offer text. Select an appropriate supported end-screen element in YouTube Studio's Editor, adjust its timing and placement, preview playback and save. Standard 16:9 videos allow up to four elements; other aspect ratios may allow fewer.
A proposed launch-film layout might finish its demonstration before the recommendation appears, leaving a visually quiet region beside the subject. This is an editorial plan, not a universal safe-zone specification. Check the actual player preview rather than copying fixed coordinates.
If the composition itself is wrong, inspect the actual-aspect-ratio delivery before adding baked-in bars to create apparent space.
Choose a destination the account supports
A recommendation can point to relevant video content; external website links have additional eligibility requirements. YouTube's guide limits external end-screen website links to YouTube Partner Program participants. A film containing a website address does not create that eligibility or make the address clickable.
Use the testable-message brief to define one sensible next action. A viewer finishing a tutorial needs a relevant continuation, not several unrelated destinations that compete with its conclusion.
Diagnose a saved end screen that a viewer cannot see
First confirm the correct video and saved configuration. Then record the viewing app or browser, device, audience setting and video type. YouTube documents context restrictions, an iPad mobile-web exception, and the viewer's ability to hide end screens. It also warns that presentation may differ from the design.
Do not repeatedly re-export the movie because one unsupported viewing context lacks the overlay. Conversely, seeing a button-shaped drawing in the picture is not evidence that a clickable element was saved.
Verify navigation and the final story together
Play the published ending in a supported viewing context, check that essential text remains readable and follow the intended element to its destination. Keep chapters and captions separate: the chapter-versus-subtitle guide explains those distinct functions. Accept a usable ending with an appropriate navigation route, without promising that every viewer will see the same overlay.
Related tasks
- Why Do My YouTube Description Timestamps Not Become Chapters?
- What aspect ratio should I use when uploading an AI film to YouTube?
- How Do I Turn a Product Launch Brief Into a Testable AI Video Story?
Sources and scope
- YouTube: Add end screens to videos: Official documentation for the controls and limits discussed above.
Based on the complete official end-screen source captured October 29, 2026. No upload, click, account eligibility or device test was performed. Proposed timing examples are editorial plans, not measured results. The source contains an iPad mobile-web exception, so blanket mobile-web availability statements are avoided.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.