How to find amazing game ideas

Every game starts with an idea: a spark of inspiration that might eventually become a finished release. The hard part is not only finding that spark. It is understanding whether the spark can become a game worth spending months or years on.

A useful game idea has two jobs. First, it gives the creator a direction: a place to begin making mechanics, worlds, characters, systems, and levels. Second, it gives the player something clear enough to understand, try, and care about. An idea that only sounds interesting in a notebook still has to become something playable.

There are many ways to find that first seed. Some ideas begin by modifying an existing game. Some begin inside a genre. Some come from a single mechanic, control scheme, real-world activity, theme, fantasy, or personal experience. And after the idea appears, it still needs to pass a few tests: can you make it, will it stand out, does it have appeal, and is it actually fun once it exists outside your head?

One reliable way to find a new idea is to start with an existing game and change something important about it. Satisfactory began from the thought of moving Factorio into first person. Subnautica's early pitch was essentially Minecraft, but underwater. Among Us drew from real-world social deduction games like Werewolf. Stardew Valley exists partly because Eric Barone wanted the spirit of Harvest Moon to be better served than it had been in years.

None of those games are simple reskins. The existing game gives the creator a starting point, but changing perspective, theme, medium, structure, or context opens a new design space. A factory game feels different when the player walks through the machines. A survival craft game feels different when the world is a deep ocean. A social deduction game feels different when deception happens through tiny animated astronauts and emergency meetings.

Influence also changes when it passes through a different person. The Japanese indie developer Ikiki made games that strongly affected designer Jonatan Soderstrom. He made his own version of Hakaiman and never released it. Later, when he teamed with musician and artist Dennis Wedin, that prototype was filtered through a different style, mood, and set of influences, and it helped become Hotline Miami. The influence is visible, but the finished game has its own identity.

That pattern is everywhere. Minecraft was influenced by Zach Barth's blocky sandbox Infiniminer. Vampire Survivors was heavily inspired by the Android game Magic Survival. Fortnite's battle royale success would not exist without the battle royale mode from PUBG. Games are always in conversation with earlier games.

The lesson is not to copy lazily. It is to stop pretending that good ideas come from nowhere. Start with the games you love, the games that frustrate you, and the games you cannot stop thinking about. Then ask what would change if the perspective moved, the theme shifted, the player goal changed, the controls changed, or the idea passed through your taste instead of someone else's.

Genre is another powerful starting point because a genre is a template. It gives you a collection of familiar mechanics, expectations, verbs, and player promises. A roguelike suggests procedural runs, risk, resources, and death. A city builder suggests placement, growth, tradeoffs, and spatial planning. A platformer suggests movement, jumps, hazards, and mastery.

One way to use genre is to find a problem and build a solution. Ryan Clark saw that traditional roguelikes often felt unfair because they leaned so heavily on randomness. That frustration helped lead to Crypt of the NecroDancer, a rhythm roguelike where the player's timing and skill matter as much as the dungeon roll. Islanders came from a related problem with city builders: the desire to build beautiful cities without the ever-expanding complexity those games often accumulate.

Another approach is to combine genres. Spelunky came from Derek Yu's love of platformers and roguelikes, plus his frustrations with both. Platformers could become repetitive when the same levels had to be replayed. Roguelikes could feel too random and opaque. Combining the two created a game where procedural spaces, platforming skill, risk, and discovery all supported one another.

You can also subtract from a genre instead of adding to it. The Captain Toad levels in Super Mario 3D World remove the jump from a character in a platforming world. That one subtraction transforms the pace and logic of the levels. A space that might normally be solved by leaping across it becomes something slower, more spatial, and more puzzle-like.

Sometimes the most productive move is to keep the mechanics but swap the metaphor. First-person shooters are often about lining up a reticle with a target, reading distance, and choosing when to act. For most of the medium's history, that has meant guns and enemies. Swap the gun for a camera and you get Pokemon Snap. Swap it for a heavy-duty pressure washer and you get PowerWash Simulator.

That is why genre should be treated loosely. Do not get trapped by every convention that makes a game "count" as a genre member. Boil the genre down to its essential DNA, then change one piece, remove one assumption, or replace the metaphor with something unexpected.

If ideas from existing games and genres feel too narrow, look outside games. Real-world activities can become strong mechanics because they already contain goals, rules, tensions, tools, and rituals. Lucas Pope spent a lot of time passing through passport control while traveling between Japan and the United States. Watching documents get checked for discrepancies helped become Papers, Please, a game about deciding who may cross a border.

Shigeru Miyamoto's interest in gardening helped inspire Pikmin. Will Wright has described ideas emerging from reading, learning, and stumbling across subjects that suddenly seem playable. The point is not to sit at a whiteboard and demand originality from an empty room. The point is to collect material from life until a subject starts to feel like a system.

Controls can also generate ideas. Luke Muscat thought about the different ways people interact with a touchscreen and noticed that a finger swipe felt like slicing. Add the image of chopping fruit, and Fruit Ninja becomes an obvious fit for the device. When Nintendo added analog shoulder buttons to the GameCube controller, Yoshiaki Koizumi associated the sensation of pressing them with a water pistol, which helped point toward Super Mario Sunshine.

A single mechanic from another game can become the seed for a whole new project. Braid grew from the idea of rewinding time, a mechanic players had seen in Prince of Persia: The Sands of Time. Yacht Club Games loved the down-thrust sword attack from Zelda 2 and spun that physical motion into Shovel Knight. A magnetic glove power-up can suggest an entire side-scrolling platformer once the designer asks what movement, puzzles, hazards, and levels would grow from that one interaction.

This is often called bottom-up design. You begin with the rules, verbs, and things the player does, then find the story, theme, and aesthetic that fit. Nintendo often works this way. Splatoon began as a mechanic about characters hiding in blobs of ink before it became a world of Inklings, fashion, music, and urban style.

The opposite path is top-down design: start with the experience you want the player to have, then find the mechanics that can create it. Hideo Kojima often works from images, moods, characters, music, and concepts before the mechanical form is fully settled. Death Stranding began from a striking mental image, then grew into a game about connection, delivery, terrain, isolation, and fragile movement.

A strong source of top-down inspiration is fantasy. What role should the player inhabit? FTL wanted the player to feel like the commander of a spaceship in a hostile galaxy, trying to keep the ship alive while everything goes wrong. Thronefall began from the fantasy of building and defending a tiny kingdom, a compact version of the ruler power fantasy.

Theme can work too. Spiritfarer began from the desire to address death and dying in a cozy, gentle way. Into the Breach came from thinking about superhero stories where city blocks are destroyed during monster fights. What if a tactics game made collateral damage the central concern?

Personal experience can also be a starting point. That Dragon, Cancer is autobiographical, built around parents facing the death of their son. But a story by itself is not yet a game idea, just as a lone mechanic is not yet a complete game idea. The starting point still has to become something the player can do.

One useful structure is to ask four questions. In an individual level or scene, what is the player's goal, or win state? What is pushing them away from that win state, or creating the obstacle? What fail state are those obstacles pushing them toward? And what actions does the player take to overcome the obstacles and reach the win state?

Crazy Taxi is a clear example. The win state is making enough money by delivering passengers to their destinations. The obstacles are the ticking timer, the other cars, and the scenery in the way. The fail state is running out of time before earning enough money. The actions are fast, reckless driving choices. That is a game idea with enough shape to build from.

If the big categories still leave you stuck, there are smaller exercises that can help.

First, break games down into tiny elements. Build a mental periodic table of mechanics and systems so it becomes easier to pick, combine, change, and remix them. Instead of thinking "make a platformer", think in verbs and rules: jump, wall slide, carry, bounce, fall, chase, hide, trade, reveal, rotate, rewind.

Second, interrogate the games you play. Develop a critic's mentality. What do they do well? What frustrates you? What problem does the genre keep avoiding? A flaw in one game can be the opportunity for another.

Third, challenge conventions. Board game designer Rob Daviau noticed that most board games reset completely after each session, as if nothing that happened before mattered. Asking what would happen if one session changed the next helped lead to Risk Legacy, where players tear up cards and permanently write on the board.

Fourth, play broadly. Do not get trapped in one genre or medium. Undertale would be a different game if Toby Fox had only looked to JRPGs and never pulled bullet-hell dodging into enemy attacks.

Fifth, impose a limitation. A blank page is scary, but a boundary gives the imagination something to push against. After Sayonara Wild Hearts, Simogo chose to make its next project slow, thoughtful, and black and white. A restriction can turn into a design identity.

Sixth, enter game jams, especially ones with strong themes. A theme works as both a limitation and a prompt. The Ludum Dare theme "Limited Space" led Tim Fitzrandolph to ask what usually needs lots of space but might become interesting with less. That helped become Parking Garage Rally Circuit, a racing game squeezed into the cramped lanes of a multistory car park.

Seventh, open the editor and noodle. Some ideas emerge from making rather than planning. A Short Hike began when Adam Robinson-Yu made a cute, cozy little scene in Unity and liked it enough to expand it into a full game.

Eighth, surround yourself with music and art. A song, painting, photo, album cover, or animation can connect ideas in ways a formal brainstorming session cannot. Kyle Gabler heard Tango Apasionado and imagined a drizzly town at sunset where people carried chairs and tables to build a giant tower. That image eventually helped become World of Goo.

Ninth, do something else. Forced brainstorming is often worse than letting the mind wander. Good ideas often arrive in the shower, on a walk, during a commute, or while doing an unrelated task because the brain has room to connect distant thoughts.

Tenth, keep the idea small. Do not try to plan an entire game on paper before testing anything. Think of the idea as a seed that will grow through prototyping, production, feedback, and revision. There is no point spending months polishing the fantasy of a game you may never make.

Once you have one idea, or several, the next question is whether any of them are worth pursuing. It is risky to grab the first idea that sounds exciting and turn it into a multi-year project without testing it. That might work, but it is closer to a gamble than a process.

Start with feasibility. Can you make this idea with your actual resources? Every developer has a different setup: time, staff, budget, expertise, experience, tools, and patience. A good idea for one team can be a disastrous idea for another.

A rough rule of thumb from Jonas Tyroller is that if you can build the gameplay prototype in one or two days, you may be able to make the game in one or two years. If the gameplay prototype alone takes two weeks, the full game may become a very long project. The point is not that the math is exact. The point is that a prototype reveals scope faster than wishful planning does.

You can also reduce scope without killing the idea. Firewatch was initially going to include other characters on the hiking trail. For a tiny team, modeling, texturing, and animating those characters was too expensive, so the story shifted to happen mostly over the walkie-talkie. The game did not lose its identity. It found a version that fit the team.

Feasibility is not only technical. You also need personal commitment. If the idea will take months or years, you need enough passion to survive the boring parts: bug fixing, iteration, content production, marketing assets, platform requirements, and the long middle where the novelty has worn off.

The next question is whether the game can stand out. A game launches into an ocean of other games. If the goal is only to make something for fun, standing out may not matter much. If the goal is to sell the game, the idea needs some chance of being noticed.

One way to think about this is the hook. Ryan Clark defines a hook as an interesting bit of information about a game that compels people to try it or talk about it. Darkest Dungeon is a good example. "A dungeon crawler" is not much of a hook. "A Lovecraftian dungeon crawler about the psychological toll of adventuring" immediately sounds more specific.

A practical test is to imagine the news headline. If a website covered the game, what would the headline be? If the strongest headline is only "new platformer" or "new dungeon crawler", the idea may not have enough visible shape yet. If the headline names a familiar genre plus a surprising pressure, fantasy, rule, or conflict, the idea starts to become easier to pitch.

But a hook can go too far. Chris Zukowski warns that a game can be so original that potential players do not understand what it is. If the idea sounds risky, confusing, or impossible to place, players may think it looks cool but move on because they do not trust it. Arco, for example, combined a Mesoamerican fantasy RPG with bullet-hell-ish real-time turn-based combat. The result was well liked by many critics and players, but the unusual pitch made it harder to sell.

That is why a hook often needs an anchor. The hook is the new thing. The anchor is the familiar thing that helps players understand how the game works. A recognizable genre, camera, control scheme, structure, or player goal can make the surprising part feel approachable.

Zachary Richman offers a useful formula: simple, with something unexpected. A tower defense game where your own bullets can hurt you is simple enough to understand, but unexpected enough to remember. Simple gets people in the door. Unexpected gets them hooked.

A hook is useful, but it is not the only way a game attracts players. Jonas Tyroller prefers to think about appeal: everything that draws someone in before they play. Appeal can come from a screenshot, a short clip, a description, a fantasy, a toy-like interaction, a challenge, a joke, a nostalgic feeling, or the promise of exploring a place.

Fantasy appeal makes a player think, "I want to be this." Exploration appeal makes them think, "I want to go there." Toy appeal makes them think, "I want to touch that and see what happens." Other games might lean on challenge appeal, comedic appeal, horror appeal, cozy appeal, or nostalgic appeal.

This is why it can be useful to think about marketing earlier than feels comfortable. You do not need final store assets before writing code, but you should be able to imagine how the idea might be shown. Lucas Pope has described thinking about whether an idea could be expressed in a trailer. If he cannot imagine a cool trailer for the concept, that is a warning sign.

Tom Francis has made a related point about names and store capsule art. Trying to figure out the name, capsule, and first public image can reveal whether the idea has a marketable proposition before you spend serious resources on it. Those exercises are not only marketing work. They are design tests. They ask whether the idea has a visible center.

A game does not need to fit one perfect sentence, and many successful games cannot be reduced to a single elevator pitch. But the creator should know what kind of appeal the game has and how that appeal could be communicated to someone who has never played it.

The final question is whether the idea is actually fun. This is where imagination is most dangerous, because brains are terrible video game simulators. Almost every idea can seem fun while it is still abstract. The hidden problems appear only when the player has to move, choose, wait, aim, fail, repeat, and understand.

A prototype turns the fantasy into evidence. It can reveal that the idea is boring, too complicated, too slow, too hard to read, too expensive, or full of design problems no one noticed on paper. It can also reveal the opposite: one tiny interaction that feels better than expected and deserves to become the center of the whole game.

The prototype does not need to prove the entire project. It needs to test the thing that makes the idea worth building. If the idea is about a strange movement rule, prototype the movement. If it is about psychological pressure in a dungeon crawl, prototype one decision under that pressure. If it is about building a tiny kingdom, prototype the build-and-defend loop. If the idea is only fun after twenty hours of content, it may not be ready as an idea.

A good game idea is therefore not just a premise, a story, a mechanic, or a genre mash-up. It is a playable direction. It has a player goal, an obstacle, a fail state, and actions. It has a hook or at least a form of appeal. It is anchored enough to understand and small enough to test. Most importantly, it can survive contact with a prototype.

That is the path from inspiration to a game worth building: collect influences without shame, change them through your perspective, look beyond games for mechanics and fantasies, reduce the idea to a playable structure, check whether it can stand out, and build the smallest version that can tell you the truth.