Quick answer: Shorts is TikTok's format with YouTube's memory: videos surface for months or years through search and recommendations rather than dying in days, and they feed subscribers into a channel where long-form devlogs and trailers live. Repurpose the same vertical clips across both platforms — the marginal cost is zero — but invest the platform-specific care in titles and the first frame, because on YouTube, search is real.

Shorts is TikTok's format with YouTube's memory: videos surface for months or years through search and recommendations rather than dying in days, and they feed subscribers into a channel where long-form devlogs and trailers live. Repurpose the same vertical clips across both platforms — the marginal cost is zero — but invest the platform-specific care in titles and the first frame, because on YouTube, search is real. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.

The half-life difference changes the strategy

TikTok videos live and die in 48 hours; Shorts keep resurfacing — a clip about your game's niche mechanic can collect views for a year as search and recommendations find new audiences. That long tail rewards evergreen framing: 'how our roguelike generates dungeons' outlives 'day 47 of development'. Build a library, not a feed.

The compounding asset is the channel itself: Shorts viewers convert to subscribers, subscribers see your long-form content, and at launch you own an audience no algorithm change fully revokes.

What to post, and the cross-platform pipeline

The formats mirror TikTok's — satisfaction clips, hook-driven devlog moments, before/after polish reveals — and the same vertical file posts to Shorts, TikTok, and Reels. Build the pipeline once: capture gameplay tall or crop deliberately, caption on-screen (sound-off viewing is common), and batch-produce weekly. The only per-platform work worth doing: YouTube titles written for search ('indie game water physics' over 'check this out'), since Shorts get found by query months later.

End-screen the funnel: name the game verbally and visually, and let the pinned comment carry the Steam link — Shorts descriptions are nearly invisible on mobile.

Shorts as the gateway to YouTube's real prize

The strategic value is the handoff: Shorts are how unknown channels get discovered, and the channel is where high-intent marketing lives — devlogs that build parasocial investment, the trailer, launch videos that subscribers actually see. Devs who built modest Shorts followings report the long-form videos converting wishlists at rates short clips never match.

So structure for the handoff: a channel page that immediately shows what the game is, one pinned long-form 'what is this game' video, and Shorts that occasionally point at it ('full devlog on the channel'). The clip catches them; the channel keeps them.

Marketing is a generosity game

The indie marketing that works rarely looks like advertising. It looks like sharing something genuinely interesting: a clip that makes people grin, a devlog that teaches something, a thread about a problem you solved. People share what makes them look good for sharing it.

So lead with the most interesting true thing about your game, not with the ask. 'Wishlist now' earns nothing by itself; a great 15-second clip earns the wishlist without asking twice.

Consistency compounds, virality doesn't

Every indie knows one game that blew up from a single tweet, and that story wrecks more marketing plans than it helps. Viral moments are lottery tickets. The reliable curve is slower: post regularly, get a little better each time, and let followers accumulate like interest.

Pick a cadence you can sustain on your worst week — one post, one clip, one devlog — and hold it for months. The audience you build that way actually shows up on launch day.

Plan for the bugs you won't see coming

Whatever else you take from this, build yourself a way to hear about problems. Once your game is on other people's machines, most failures happen out of sight: the crash on hardware you don't own, the save that corrupts once in fifty exits, the bug players mention in a review instead of a report.

A lightweight crash and bug reporting setup — even just Bugnet's free tier wired into your engine — turns that silence into a fixable list. The devs who look calm at launch aren't luckier; they just see their problems earlier.

Putting it to work

Don't try to act on all of this at once. Pick the one change that costs you the least and pays the most this week, do it, and see what actually happens before reaching for the next.

Most of this rewards steadiness over intensity. A small improvement made every week, checked against how real players respond, outruns any single burst of effort — in this corner of game development and every other one.

Show up where your players already are, lead with the interesting thing, and keep the cadence.