Case Studies

The stories behind 10,000+ thumbnails

Portfolios show images. Case studies show how the work actually happened — the volume, the systems, and the testing behind channels where thumbnails drive growth.

Case Study 01 · LankyBox Main Channel

Managing thumbnails at massive YouTube scale

3.5 years9M → 42M+ subscribersUp to 10 uploads/dayThousands of videos

For around 3.5 years, I worked inside the LankyBox thumbnail pipeline during one of its biggest growth periods. I started when the main channel was around 9M subscribers and left when it had grown past 42M. During that run, the channel operated at extreme upload volume — at peak, around 10 videos per day, every day, for a long time.

At that scale, a thumbnail isn't a one-off design job. It's a production system: versions, swaps, tests, naming, consistency, and speed. My job was to keep that system fast and the thumbnails clickable.

My role in the pipeline

  • Creating launch thumbnails on tight daily deadlines
  • Managing thumbnail swaps across the library
  • Reviewing CTR and view performance patterns
  • Building A/B/C test variations
  • Creating bonus thumbnails
  • Supporting compilation thumbnails
  • Keeping visual consistency across a huge library
  • Managing thousands of assets and versions
  • Improving thumbnails based on real performance data
I contributed to the thumbnail pipeline during a period where the main LankyBox channel grew from around 9M to 42M+ subscribers. My work focused on fast, clickable, consistent thumbnails built for a high-volume upload machine — I don't claim the growth, but I kept the thumbnails competitive while it happened.

Case Study 02 · LankyBox World

Building thumbnail systems from the beginning

Near-zero → 1.1K+ uploadsNow ~10M subscribersThumbnail managerRoblox · Gaming · Animation

I started working on LankyBox World when the channel had little to no uploads. By the time I left, it had around 1.1K+ uploads — and the channel has since grown to around 10M subscribers. I managed the thumbnails across that entire run, creating many of them myself.

Starting near zero meant the visual identity didn't exist yet. The work included building a consistent look the audience could recognize in the feed, improving click appeal upload after upload, supporting Roblox and animation content, and adapting thumbnails for a younger gaming audience — readable, bright, and instantly clear about what the video delivers.

A lot of that thumbnail work performed strongly and helped shape the visual style the channel became known for.

Case Study 03 · A/B/C Testing & Swaps

Designing with data, not guesswork

Before YouTube had native A/B testing tools, our team tested thumbnail variations manually — through swaps, alternative versions, and close performance tracking. I reviewed CTR, views, and audience response to understand which visual ideas actually earned clicks, and which just looked good in a folder.

That experience changed how I design. Every thumbnail decision — expression, scale, color, composition — is a testable hypothesis, not a matter of taste.

What we tested

Different facial expressionsCharacter scaleBackground colorsMore direct storytellingCleaner focal pointStronger contrastSimpler object placementBetter emotional hook

How a test actually ran

swap-log — one upload, one test cycle
DAY 0Launch thumbnail goes live with the uploadBASELINE
DAY 2CTR tracking under channel averageFLAGGED ⚠
DAY 2Swap in V2 — bigger expression, cleaner focusSWAPPED
DAY 5V2 outperforms V1 on CTR and viewsWINNER ▲
DAY 6Pattern noted → applied to the next uploadsLOCKED ✓
next upload, same discipline

WHAT THOUSANDS OF TESTS TAUGHT ME

  • 01

    Emotion reads first

    A clear face beats a busy scene at feed size. Expression is the hook.

  • 02

    One story per thumbnail

    Split attention kills clicks. Every winning variant told exactly one thing.

  • 03

    Contrast beats detail

    If it needs a zoom to understand, it fails. Winners read at 120 pixels wide.

  • 04

    The feed decides, not taste

    The 'prettiest' version often lost. Swap fast, watch the data, keep what wins.

REPRESENTATIVE CYCLE — EVERY MANUAL TEST FOLLOWED THIS LOOP, YEARS BEFORE YOUTUBE SHIPPED NATIVE A/B TOOLS.

Want this kind of system on your channel?

Let's talk