The short version
- Players follow people they can picture. Show the desk, the sketch and the person fixing the bug.
- A playtest call is the easiest post to write and the most useful to your game.
- Say what changed in the game, not the build number.
- 3 posts a week is enough: one game post, one request for feedback, one person or place.
You've got a build that's finally fun and a Facebook Page with a logo and nothing else. If you're looking for game studio social media post ideas, you probably also have a day job, a deadline and a lot of art.
Here are 16 posts that use what you're already making. They're written for a small studio, and they work for the players, the testers, the local press and the next hire.
What game studio social media post ideas should show
- One moment from the game that makes someone say 'oh nice.'
- A real person, name and role, near the screen.
- A clear way to help: play, test, share or wishlist.
- The truth about dates. Say 'later this year' if you're not sure.
A quiet page needs a good photo habit. How to take good photos for your business page with a phone works for desks and screens too. Hardware teams can borrow from electronics company post ideas.
Show the game in progress
Devlog of the week
This week in [game name]: [one change]. Here's a 10-second clip. It took us [number] days to get the jump to feel right, and we think it finally does.
Photo: A short clip frame of the new mechanic.
Sketch to screen
Left: [artist]'s first sketch of [character]. Right: how [character] looks in the game today. We kept the hat.
Photo: A sketch beside the finished sprite.
Sound of the week
Our composer [name] recorded this sound using a [everyday object]. Turn up the volume and guess what the sound is in the game.
Photo: The everyday object next to a microphone.
The bug that made us laugh
Today's bug: [funny description]. We kept it in for the day and then fixed it. We have the clip, and it's staying in the vault.
Photo: A screenshot of the funny glitch.
Playtests, patches and feedback
Asking people for help feels risky. It's the best thing a small studio can do, because it makes players part of the team.
Playtest call
We need [number] players to try [game name] before it goes out. It takes about 30 minutes, you'll see it first, and your name goes in the credits if you want. Comment 'in' for a link.
Photo: A controller on a desk next to a laptop.
Patch notes in plain words
Patch [number] is live. We fixed [problem], made [thing] a bit easier and removed the door that wouldn't open. Thanks to everyone who sent a clip. Keep them coming.
Photo: A screenshot of the fixed area.
What you told us
You told us the first level is too long. We listened and cut it in half. Thanks to [first name] for the kind but honest note.
Photo: Two level maps side by side.
Vote on a feature
Should the next update add [option A] or [option B]? Vote in the comments. We'll announce the winner on Friday and build it next.
Photo: Two mockups on a whiteboard.
Behind the screens
Our corner
This is where [game name] is made: a spare room, two monitors, one very old couch and a dog named [name]. Come say hi at the next [local event].
Photo: The workspace with the dog in frame.
Meet the programmer
Meet [name], who makes the characters move and the code behave. Ask [name] anything about how a game gets built. Replies are open.
Photo: A relaxed photo with a controller.
Our tools, plainly
We use [engine/tool] and a lot of sticky notes. Here's the board where we track what's done and what's on fire.
Photo: A wall of sticky notes in columns.
We're hiring
We're hiring a [artist/programmer/QA] in [town] or remote. Small team, real shipping, fair hours. Send a link to something you've made, even a small one.
Photo: A desk with a tablet and a pen.
The studio and the local scene
Local game jam
Spent the weekend at [jam name] in [town]. Built a small game in 48 hours and slept in 4. Thanks to the organizers for the pizza.
Photo: A team at a table, laptops and cups.
Convention booth
We'll be at [event] on [date] with a playable build of [game name]. Stop by, say hello and tell us what you think. We'll be the ones looking nervous.
Photo: The booth banner and a table, set up.
Student visit
A class from [school] visited the studio today. They asked how we make a character. We showed them. Their questions were excellent.
Photo: A group of students around a screen, with permission.
Thanks to the neighbors
Thanks to [local cafe] for letting us borrow a corner on deadline days. Our best level was designed on one of your napkins.
Photo: A napkin sketch of a level.
A simple week of game studio posts
3 posts a week
- TueGame postA clip, a sketch or a sound.
- ThuFeedback postA playtest call, a vote or patch notes.
- SatPerson or placeA teammate, a jam or the desk.
Wondering about the right pace? How often a business should post on Facebook gives a rule of thumb.
What makes a studio page look dead
Do
- Show real game footage, not a render.
- Credit the artist or tester by first name.
- Be honest about delays.
- Reply to comments, even short ones.
Don't
- Promise a date you can't keep.
- Post another studio's art as your own.
- Use players' names or photos without asking.
- Argue with critics in the comments.