What to Post on X as a Game Developer: 15 Proven Ideas

Most game developers post the same three things on X: a trailer, a screenshot and a line asking people to wishlist. Then the build changes, a fest starts or ends, and the account goes quiet for a month. The work itself is not the problem. The problem is that the things you do every day, like a sprite redraw or a bug you fixed at 2 a.m., never get turned into a post.

You also work under rules most creators do not face. Music in a clip gets flagged by automatic detection, Steam wants store screenshots of the game itself, and you can enter only one Steam Next Fest per game. This page gives you 15 ideas you can film or write this week. Each one has a template in your words, and most come with a real post that shows the idea working.

All 15 ideas at a glance

#IdeaFormat
1Same room, one year apart: last year's build vs this week's buildSingle image or a short video (under 140 seconds)
2Why I redrew every sprite in [game] after [N] monthsText thread (3 to 6 posts)
3[Game] [version] patch notes, shown in one clipShort video (under 140 seconds) or GIF
4The game is about [N] percent done. Here is what is left.Text post with one GIF or screenshot
5The one [engine] setting that fixed my [problem]Text post with a screenshot of the setting
6Postmortem: the [system] I cut from [game] and whyText thread (3 to 6 posts)
7Where the music in my trailer came from, and the license for each trackText post or single image with a credit list
8Why most of your wishlists come from people who never play the demoText thread (3 to 6 posts)
9[N] wishlists. Here is where the last [N] came from.Text post
10Steam says my demo was one of the most played in this festText post with a screenshot of the Steam message
11Where my wishlists came from this month, by channelText thread (3 to 6 posts) with a short table image
12Week [N] of my Steam page: the numbers, and what I change nextText post with a screenshot of the page stats
13Playtest call: I need [N] people to test [one system] this weekText post, with the sign-up link in the reply
14The funniest bug from this week's playtests, and the fixShort video (under 140 seconds) or GIF
15Next Fest starts [day]. The demo is [N] minutes of [what the player does].Short video (under 140 seconds) or single image, with the demo link in the reply

Why X works for game developers

X is where players who follow games, other developers and streamers look for what is coming next. A devlog post can reach someone who would never search for your game on Steam, and a developer who replies to your build clip may share it with their own followers. Your posts only need to make sense to a player who has never opened an engine.

Keep hashtags to three or fewer, and use the ones your genre and the current event already use, like the Next Fest tag during a fest. Put your Steam link in a reply, not in the main post, so the post itself stays about the game. Pin one post that explains the game in one sentence and links the page.

  • Short video (under 140 seconds): A build clip shows movement, which a still screenshot cannot. Accounts without a paid X subscription are capped at 140 seconds, so cut each clip to the one change it shows. Export as an MP4 at 1280 by 720 pixels, which is a safe size for X.
  • GIF (a short looping clip): A loop of one animation, hit effect or UI transition shows progress in a few seconds, and it works with the sound off. Most players in a feed will see the loop before they read the caption.
  • Text thread (3 to 6 posts): Postmortems, wishlist breakdowns and design decisions need words. Keep each post to one point so the thread reads as a series, and put the image in the first post.
  • Single image with a short caption: Before and after pairs, sprite comparisons and channel tables read in one glance. Use captures from the game, since Steam's rules for store screenshots ask for shots of the game itself rather than concept art or stills with text on them.

15 X content ideas for game developers

Show the build

These posts put the game on screen, so people see progress instead of a promise.

Single image or a short video (under 140 seconds)

1. Same room, one year apart: last year's build vs this week's build

Why it works: Players who already follow your game want to see that it is getting better, and other developers want to see what a year of work looks like. Pick one screen, such as a level, a menu or a boss arena, and capture it from the same camera position in each build. The comparison reads without a caption, so one line of context is enough.

TemplateSame [level or screen] in build [old version] and build [new version]. [N] months of work, mostly on [the change]. Which one would you rather play?
Two builds of the same scene, and the post names the age gap and the one thing that improved.X

Text thread (3 to 6 posts)

2. Why I redrew every sprite in [game] after [N] months

Why it works: Players who saw the old art will notice when it changes, and a reason in the first line keeps them from thinking the change was a mistake. Solo developers often change their style as the game grows, and they can show old and new sprites side by side with the reason for the change. This is the post that players and artists reply to with their own experience.

TemplateI was drawing the [N] new sprites for [update] and noticed my art style had drifted from the first build. Old on the left, new on the right. I redrew [N] sprites so [reason, such as the characters match the new levels].
The reason for the change is in the first sentence, before any image.X

Short video (under 140 seconds) or GIF

3. [Game] [version] patch notes, shown in one clip

Why it works: Players who wishlisted or bought the game want to know what changed since the last build. A clip that shows the fixed bug and the new feature in one take is faster to read than a list of changes. Put the full patch notes in a reply so the post stays short.

Template[Game] [version] is out. Three changes in this clip: [fix one], [fix two], [new feature]. Full notes in the reply. Tag: [genre] gamedev
The update is announced in one line, with the devlog link and two hashtags, and the GIF does the rest.X

Text post with one GIF or screenshot

4. The game is about [N] percent done. Here is what is left.

Why it works: A solo developer who names the open tasks gives people a reason to check back, and the list makes the schedule look real. Name each task, such as art for a level, the final boss or the audio pass, instead of writing polishing. Players who wishlisted the game can see the work and not only a release date.

Template[Game] is about [N] percent done. Still to do: [art for level X], [boss X], [audio pass]. Next build lands [week]. Which of these would you want to see first?
The percentage and the open work come in the first two lines, with the art still to come named as the next step.X

Engine and production know-how

These posts answer the questions other developers ask in replies, with the exact setting, step or decision.

Text post with a screenshot of the setting

5. The one [engine] setting that fixed my [problem]

Why it works: Other developers search for the exact setting name when a build stutters, so a post that names it is one they can use right away. Show the setting in the editor or config file, give the value you used, and say what changed on screen. Use the engine name your community searches for, such as Unreal or Godot.

TemplateIf your [engine] game [symptom, such as stutters every few seconds], check [setting name] in [where it lives]. I set it to [value] and [what changed in the frame time or on screen]. Tested on [platform]. Tag: [engine] gamedev
The exact console variable is in the first line, so a developer can search for it and try it.X

Text thread (3 to 6 posts)

6. Postmortem: the [system] I cut from [game] and why

Why it works: Solo developers and small teams are the readers most likely to be stuck on scope, and a cut system is an honest example of it. Name the system, how many weeks it took and the moment you decided to cut it. A player learns that the game was shaped by choices, and a developer learns a rule they can use.

TemplateI cut [system] from [game] after [N] weeks. Three reasons: [reason one], [reason two], [reason three]. What stayed: [the part you kept]. Thread below.
The short bullet summary sits in the first post, and the full write-up is linked after it.X

Text post or single image with a credit list

7. Where the music in my trailer came from, and the license for each track

Why it works: Streamers and press who reshare a trailer need to know what music is in it before they post. A clear list of each track, its source and its license means nobody has to ask. The safe sources are music you can name and license: a free library, a subscription service, or music a studio has released for creators.

TemplateMusic in the [game] trailer: [track name] by [artist], from [source, such as a subscription library], licensed for [use]. Gameplay clips in this post use [the game's own sound / no music]. Credits in the reply.

Text thread (3 to 6 posts)

8. Why most of your wishlists come from people who never play the demo

Why it works: Many developers spend most of their effort on the demo and too little on the store page. Between 68 and 88 percent of wishlists come from players who never touch the demo, so the page does most of the selling. A thread that explains this and walks through your own page, one section at a time, gives developers planning their own fest a checklist to use.

TemplateBetween 68 and 88 percent of wishlists come from people who never play the demo. Here is my store page as a first-time visitor sees it, and the three things I would change first: [item], [item], [item].

Proof and wishlist results

These posts share real numbers. A post with a number and a plain explanation of where it came from is the one other developers reply to.

Text post

9. [N] wishlists. Here is where the last [N] came from.

Why it works: A wishlist milestone gets shared, and a breakdown turns it into something other developers can use. Give the total, the number that came during the fest or sale, and the one thing you did in that window. Developers at the same stage will recognise the situation and reply with their own numbers.

TemplateWe just hit [N] wishlists. [N] of them came during [Steam Next Fest or the sale]. What we did that week: [action one], [action two]. Next goal: [N] by [date].
The milestone and the number from the fest are in the same line, with the next goal named at the end.X

Text post with a screenshot of the Steam message

10. Steam says my demo was one of the most played in this fest

Why it works: A ranking email from Steam is a number that no one can argue with, and it shows that players spent real time in your demo. Post the message, the wishlist count, and what is still left before launch. Developers who are heading into their own fest will want the details.

TemplateSteam just emailed me that [game] was one of the top [N] played demos in [fest name]. It is at [N] wishlists. Full release is [N] weeks away. Still to do: [item one], [item two].
The Steam email is quoted in the first line, and the next steps follow the number.X

Text thread (3 to 6 posts) with a short table image

11. Where my wishlists came from this month, by channel

Why it works: Most developers guess which channel works. A post that lists each channel with the wishlists it sent is a real answer, and it shows which posts to repeat. List only the channels you posted to, and say which one converted best and why.

TemplateBreakdown of [N] wishlists this month. [Channel one]: [N]. [Channel two]: [N]. [Channel three]: [N]. The best one for me was [channel] because [reason]. Ask me about the Steam page in the replies.
The post lists the channels it tried and says which one converted best, in the developer's own words.X

Text post with a screenshot of the page stats

12. Week [N] of my Steam page: the numbers, and what I change next

Why it works: A slow week with real numbers is the kind of post that solo developers reply to. Give impressions, page visits and wishlists side by side, since the gap between visits and wishlists shows where the page loses people. Then name one change and report on it next week.

TemplateWeek [N]: [N] impressions, [N] page visits, [N] wishlists. Most people leave between [visits] and [wishlists]. This week I am changing [one thing on the page]. I will post the same numbers next Monday.

Playtests and fest moments

These posts ask players for one specific thing, or give them a reason to play this week.

Text post, with the sign-up link in the reply

13. Playtest call: I need [N] people to test [one system] this week

Why it works: A specific test request gets more replies than a general line asking people to play. Name the one system you need checked, how long it takes and how people sign up. Testers who try one thing give you feedback you can act on.

TemplatePlaytest for [game]: I need [N] people to try [system, such as the new inventory] for about [N] minutes. Build [version] runs on [platform]. Reply with [sign-up method] and I will send the key.
The post is a short call with the playtest name and a link, and nothing else asked of the reader.X

Short video (under 140 seconds) or GIF

14. The funniest bug from this week's playtests, and the fix

Why it works: A glitch clip stops people in a feed, and a bug shows that the game is in testing. Post the clip, say what caused it in one line, and say which build fixed it. Showing the fix in the next post closes the loop for anyone who followed the first one.

TemplatePlaytest bug of the week: [what happens on screen]. Cause: [one line]. Fixed in build [version]. Post your worst bug in the replies.

Short video (under 140 seconds) or single image, with the demo link in the reply

15. Next Fest starts [day]. The demo is [N] minutes of [what the player does].

Why it works: A fest countdown tells players when the demo goes live and gives them a day to act. Post on the days that matter: the day the fest opens, the midpoint and the last day. You can enter only one Steam Next Fest per game, so this post is one to get right.

TemplateSteam Next Fest starts [day]. [Game] demo is live from [day] for [N] minutes of [what the player does]. Demo link in the reply.

Best practices for X as a game developer

How often to post

Start with two posts a week: one build clip or update, and one idea from this page. Reply to players and developers every day, because the replies bring people to your profile. During a fest, post on most days of that week. Pick a rhythm you can keep for 90 days, since a steady pattern does more than a burst followed by silence.

Tools that help

  • Steamworks partner dashboard: Check wishlist, page visit and impression numbers before you write any milestone or channel post, so the figures in the post are the ones Steam reports.
  • itch.io: Host the full devlog there and link to it from a short X post, so the post stays a clip and the details live on the page.
  • presskit.gg: Turn your Steam page into a press kit that streamers and press can open before a fest, and link it from your pinned post.
  • Sycamore: Add captions to a build clip or a playtest clip so people can follow it with the sound off.

Do

  • Film the build as it runs, not concept art. Steam's store screenshot rules ask for shots of the game itself, and a build clip does the same job on X.
  • Put your Steam link in a reply, not in the main post, so the post stays about the game.
  • Write down the source and license of every track in a trailer or clip before you post it.
  • Name the exact setting, file or bug in the post, so another developer can act on it the same day.
  • Use the same post type for a month and compare the wishlists it sent, so you know what to repeat.

Don't

  • Don't put the game's soundtrack or any licensed track under a clip. Automatic detection can strike or demonetize a video even when the game footage is fine.
  • Don't lead with AI-generated or AI-retouched art. It makes the page look unfinished to the players you want to reach.
  • Don't use more than three hashtags in a post. Extra tags make the post look like spam to the people you want to reach.
  • Don't send Next Fest traffic to a store page that isn't ready. Most wishlists come from the page, not the demo.
  • Don't post a milestone without a next goal. A milestone with no next step reads as the end of the story.

More content ideas

More X ideas: Indie Hackers, Newsletter Writers, Crypto Projects, Freelance Marketers

Edit your videos to go viral