Which Steam update post should I use?

Use the smallest type that fits. Steam has three update event types: Patch Notes, Regular Update and Major Update. Valve designed Patch Notes so that they do not push aside your bigger news, and Major Updates for the biggest moments of the year. A Regular Update sits between the two.

A Major Update needs more work: a title, a rich description with images, and an 800 x 450 cover image. Patch Notes need only a title and a description.

Where Patch Notes and Major Updates show on Steam, from the Steamworks documentation.
Post typeUse it forWhere it shows
Patch NotesFixes and small changesThe Downloads window, the News Hub and the Library detail page in compact form; the latest is linked from the store page. Not in the Library What's New section.
Major UpdateNew content and the big moments of the yearLibrary What's New, the game's Library page, one of the two events on the store page, the News Hub, the Downloads view, and the store home page with an Update Visibility Round

Sources: Steamworks Patch Notes, Major Update and Events and Announcements Visibility documentation.

What should I ship in the first two weeks?

Fixes, fast, as small patches. A player who hits a crash early can refund: Steam accepts refund requests within 14 days of purchase with less than 2 hours of play. Read crash-free sessions and top errors by build every day, and fix the worst one first.

When you upload a build with SteamPipe, Steamworks prompts you to post patch notes right away. Use it. Valve says patch notes help customers see that you keep working on the game. Link each post to its build, so players can open it from the Downloads view. This works only for current and future builds.

Sources: Steam Refunds policy; Steamworks Patch Notes documentation; Manalens error tracking documentation.

How do I choose what goes in the first major update?

Pick it from evidence, not from the loudest thread. Use where players quit, what breaks and what the reviews repeat. The table matches each signal with a type of update.

Valve's advice for announcements fits here too: have a goal, and if players are confused by a feature, fix the cause in the game instead of explaining it in a post.

Signals to read before you plan an update, and what each one suggests (our guidance).
SignalWhere to read itWhat it suggests
A level or step where many players stopFunnel chart or levels table, by buildA difficulty or clarity fix
A crash or error that many players hitTop errors on the Game health boardA stability fix before new content
A theme that repeats in recent reviewsSteam reviews, read with a time limitA change that players ask for
Low D7 for new playersRetention by install cohortA better first session before more late content

Sources: Steamworks Events and Announcements Tools documentation; Manalens funnels, retention and error tracking documentation.

How often should I ship major updates?

Rarely enough that each one is big. Each product starts with five Update Visibility Rounds, shared between Early Access and full release, and Valve may grant more to products that sell well. A round can start only after your launch visibility has ended. It runs up to 30 days or 1 million home page impressions, and it needs an announcement from the last 30 days.

Rounds do not show during the big seasonal sales, but those days still count toward the 30 days. So start a round in a quiet week.

Pair a major update with a discount when you also want new buyers. Valve shows sale events mainly to prospective buyers and update events to owners. Dome Keeper went from about 200 to 5,274 concurrent players after a free update that shipped with a 60% discount.

Sources: Steamworks Update Visibility Rounds and Events and Announcements Visibility documentation; Game World Observer (10 October 2023).

Should I post a public roadmap?

Yes, if it sets honest expectations. Valve's Early Access rules say not to make specific promises about future events, because you cannot know when or whether a feature will ship. The same care helps a released game. Show what you work on now and what you think about next, without dates you cannot keep.

Pin the roadmap on your Community Hub or post it as an announcement. Valve suggests that only one or two events stay visible on the Library home page, because many old events teach players to ignore your posts. Hide an old teaser when a new one goes up.

Sources: Steamworks Early Access and Events and Announcements Visibility documentation.

How do I write an update post that players read?

Lead with what changed for the player, and use the Steam tools that make a big post stand out.

  • Start with what changed for the player, then give the details.
  • Use section headers, lists and tables. Images in the body show at up to 800 px wide.
  • Translate the post if the game supports other languages. Steam shows each player their language and falls back to English.
  • Turn on Featured Event for a big update. Steam pins it at the top of the game's Library page until the player sees it, then for 48 more hours.
  • Stage the post ahead of time with the visibility settings. The Library can take up to an hour to show a new event.

Sources: Steamworks Events and Announcements Tools and Visibility documentation.

How do I know if the update worked?

Compare players on the new build with players on the old one over the same number of days. For the Steam side, compare daily wishlist adds and units during the visibility round with a quiet baseline before it. Our guides on update impact and on event lift show each method step by step.

Sources: Manalens retention documentation; Steamworks Wishlists documentation.

How do I see which build my players run?

Manalens is the analytics and growth engine built for games. Set the version and build when you start the SDK. Every event then carries them, so the Game health board and any funnel or retention chart can be split by build.

Sources: Manalens product documentation.

Frequently asked questions

Do Steam patch notes show on the Library home page?

No. Valve keeps Small Update / Patch Notes posts out of the What's New section at the top of the Library home page. They show in the Downloads window, in compact form in the News Hub and on the Library detail page, and the latest patch notes are linked from the store page.

Can I use an Update Visibility Round right after launch?

No. Valve says you can start a round once your initial launch visibility has ended. Each product starts with five rounds, shared between Early Access and full release, and each round needs a community announcement from the last 30 days. A round runs up to 30 days or 1 million impressions.

Should I put dates on my roadmap?

Only dates that you are sure of. Valve's Early Access rules say not to make specific promises about future events, because you cannot know exactly when a feature will be done. Show what you build now and what comes after, and post the date when the update is ready.

How fast should I fix bugs after launch?

Fix crashes within days, because Steam accepts refund requests within 14 days of purchase when the player has played for less than 2 hours. Ship each fix as a small patch with patch notes linked to the build, and keep new content for a Major Update.

Sources and implementation