I Built a Free YouTube End Screen & Card Generator (Because Canva Charges $12.99/month)
Stop paying $12.99 per month for Canva Pro when you just need a clean YouTube end screen.
I was tired of Canva's subscription model — $12.99/month for a tool that basically just lets you pick colors and add text. For YouTubers who just need a professional end screen once in a while, that's ridiculous. And YouTube Studio's built-in end screen editor? Limited to presets and requires a Google account every time.
So I built something better.
YouTube End Screen & Card Generator runs 100% in your browser.
What you get:
- 1280×720 standard YouTube end screen size (16:9)
- Solid colors or gradients with 12 curated presets
- Add CTA headline and subtext with customizable font size and color
- Video card placeholder — position it with X/Y sliders
- Follow button placeholder — position it with X/Y sliders
- Upload your own thumbnail images for video cards
- Pre-built card templates (Video Card, Subscribe Button, End Screen Card)
- Toggleable safe area guide so your elements land in the right spot
- Download as high-quality PNG — no watermark, no signup
- Works offline after first load
- Free forever
The free tier gives you everything you need. No paywalls, no watermarks, no tricks.
vs Canva: $12.99/month. vs YouTube Studio: no signup, full design freedom. This is free.
Built for YouTubers who want a professional end screen without the subscription.
Top comments (1)
"Free, no upload, no signup" is the right wedge against Canva's paywall — client-side tools win on trust because the user can verify the claim in the network tab.
I ran a quick launch check on the tool page. TLS is fine (Let's Encrypt, TLS 1.3) and the SEO basics are solid — title, meta description, canonical, robots.txt and sitemap all live. The gap: all six browser-security headers are missing. HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy — none set. For a tool whose pitch is "your images never leave your browser", CSP is the one that makes it structurally true:
default-src 'self'blocks even a compromised dependency from exfiltrating what a user drops in.You're on bare nginx (1.20.1 per the Server header), so this is one config block — six
add_headerlines in the server block, reload, no redeploy. While you're in there:server_tokens off;, since the header currently hands anyone an exact nginx version to match CVEs against.Two smaller things from the same pass: TTFB is 807ms (worth a look at caching — the rest of the page is light), and there are two
<h1>tags where one is the convention crawlers expect.Happy to re-scan once the headers land and confirm it's green.