Changes coming to Steam Greenlight

This new direct path “Steam Direct” described in our post linked above will entirely replace Greenlight. So a week or two before we activate this new path, we'll stop accepting new submissions in Greenlight.



In the meantime, if you are considering posting your game to Greenlight, please do so.



We’ve always evaluated and Greenlit titles that we feel we have enough data on, either in terms of customer votes or success on other platforms, awards, kickstarters, or other similar inputs. We plan to continue Greenlighting titles that have sufficient community interest until the release of Steam Direct. At that point, any games that we didn’t have sufficient data to Greenlight will be invited to use the new onboarding path and app fee if they are still interested in bringing their product to Steam.



If you paid the Greenlight Submission Fee and don’t have any Greenlit titles, you can get a refund of your Greenlight Submission Fee. You can choose to request this refund now, or you can wait and request the refund once we make the transition to Steam Direct if your submission still has not been Greenlit.



We have a couple more internal tools we need to complete and we want to allow some time to account for feedback or suggestions from the community. So there isn’t a specific timeline at this point, but we expect to be able to make this transition sometime in the next few months.



If you already have a Greenlit title, but haven't completed the digital paperwork to set it up in Steamworks yet, there's no need to worry. Once a title has been Greenlit, you have an invitation for that game to come to Steam. That invitation doesn't expire with any of these changes.

2/10/2017 – Today we shared some information on where we’re headed with the next evolution of Steam Distribution. You can read the full announcement here: http://steamcommunity.com/games/593110/announcements/detail/558846854614253751. There are a couple questions you might have regarding Greenlight that we didn’t get to cover in that blog post, so we’re doing so here: