What Story Games Actually Is
Story Games is a free, community-run website where people post interactive fiction and text-based games for others to play directly in the browser. The URL is storygames.org. You don't install anything. You create an account, browse games, play them, and optionally write your own. The platform focuses on short-form interactive stories rather than traditional video games. Think of it like a hybrid between a text adventure archive and a creative writing community. Most games are built with common IF (interactive fiction) parsers, and the site handles the hosting and execution on their end so players never need any special software.
Why People Use Story Games Instead of Other Platforms
There are other places to share interactive fiction. Twine, itch.io, the Interactive Fiction Database, and the IF Wiki all exist. Story Games carved out a specific niche by requiring every game to include an "interactive reading experience" tag, which basically means the game has to involve meaningful player choices that change the story. It filters out a lot of the pure prose fiction that floats around on other sites and keeps the focus on interactivity. I spent a few weeks trying to promote a project I was working on across multiple IF platforms, and the main difference I noticed with Story Games was the comment system. Comments on Story Games are tied to specific moments in the game text, not just general feedback at the bottom of a page. This sounds minor but it changes how people give notes. Instead of saying "the middle part was slow," someone can click on a specific passage and say "this choice here felt meaningless." That level of detail is genuinely useful when you're iterating on a draft. The tradeoff is that the comment system requires players to have an account and log in before they can leave feedback. That creates friction. Some people will just play and leave without commenting because the signup wall stops them. I watched one of my own games get about forty plays in the first week and only three comments, all from established community members. A game on a less gated platform might have gotten fifty comments from casual visitors who didn't care about creating an account.
Another thing nobody mentions enough: Story Games has a strict content policy around NSFW material. If your interactive fiction contains explicit sexual content, it will be removed. This isn't a vague policy. I've seen games taken down within hours of being posted for borderline content that would be completely acceptable on itch.io or in the Choice of Games community. If you're making mature-themed IF, you need to decide early whether Story Games is the right home for it or whether you should host elsewhere and just use Story Games for discovery. Some authors post a censored version on Story Games and link to the full version on their own site, but that's a workflow decision you make upfront. The site also supports basic analytics through their built-in play tracker. You can see how many people started a game, how far they got, and where they dropped off. This data is modest compared to what you'd get from a full web analytics setup, but it's immediately available without configuring anything. I once found a puzzle in my game that about sixty percent of players got stuck on by looking at the drop-off point in the analytics. The fix took about twenty minutes. Without that data point, I might have spent weeks wondering why feedback kept saying the same section was broken.
Get the Full Details
How to Get Started
Create an account at storygames.org. It's free and only requires an email address. After signing up, you can start browsing games immediately. Use the search and filter options to sort by genre, length, parser type, and rating. The rating system is simple — upvote or downvote after playing — and it accumulates over time. To publish a game, you'll need to write it using a supported format. The most common approach is to use the Ink language, which Story Games natively supports. You can also use Inform 7, Twine (Harlowe or SugarCube passages), and a few other formats. Once your game file is ready, you go to the submission page, upload your story file, fill in the required metadata (title, description, genre tags, content warnings), and submit it for review. The review process usually takes between a few hours and two days, depending on the current queue. The metadata fields matter more than people expect. Story Games uses tags and genres for its discovery algorithm. If you tag your game incorrectly or leave fields blank, it simply won't show up in relevant searches. I've seen games sit at zero plays for weeks because the author didn't select the correct parser tag, so the site's filter couldn't surface it to the right audience. Double-check every field before submitting.
There's also a community Discord attached to Story Games if you want real-time discussion, but the main activity happens on the site itself. The Discord is optional. Most regulars don't use it.
Common Problems and What Actually Works
One issue that comes up repeatedly is save state management. Story Games handles saves automatically for supported parsers, but there are edge cases. If your game uses custom JavaScript or non-standard state tracking, the automatic save system can break. I ran into this with a game that tracked player inventory across multiple chapters using a custom variable system. The saves worked fine during my local testing, but once uploaded, the game would load a save from chapter three and then lose all the inventory data because the parser was resetting custom variables on load. The workaround was to move the inventory into the parser's native persistent variable system instead of my custom one. It took about an afternoon of restructuring the code, but the game has been stable ever since. Another problem is mobile play. Story Games games are browser-based, so they work on phones, but the text display and choice buttons are optimized for desktop screens. Players on mobile report that some games feel cramped or hard to tap accurately. If you're writing for Story Games, test your game on a phone before publishing. It takes ten minutes and saves you a bunch of negative feedback. The platform's algorithm tends to favor games that get quick engagement in their first forty-eight hours. Games that don't get plays early tend to stay buried. This means day-one visibility depends heavily on whether you have an existing audience to drive initial plays, or whether you share the link in relevant communities. There's no guarantee the site's own discovery mechanism will pick up a new game without that initial push. I've seen games with better writing and more polished mechanics get fewer plays than simpler games just because the author posted on a Friday night when the community was quiet versus Monday morning when everyone was checking new submissions.
If you're looking for an alternative for a similar purpose, itch.io has a larger interactive fiction section and doesn't have the same content restrictions, but it lacks Story Games' integrated play system and moment-specific comment feature. You'd host the game files yourself and manage your own analytics. It's more work upfront but gives you more control long-term. Story Games works well if your goal is reaching an audience that actively reads and reviews interactive fiction. It doesn't work well if you're making experimental or adult-oriented IF, or if you expect the platform to promote your game without you doing anything to share it. Be honest about what you're making and whether this fits, before you spend time building for it.
