Cool Math Games Mini Metro

What Mini Metro Actually Is

Mini Metro is a transit-building puzzle game. You design metro lines for a growing city by connecting stations with colored lines. The stations multiply over time. Each station needs a passenger picked up every few seconds. If a station backs up past its maximum capacity, the game ends. That is the entire loop. Simple to pick up, easy to lose sleep over. I picked it up years ago thinking it would be a casual time sink. That was my first mistake. The game punishes autopilot thinking. Once the city expands into its later shapes, you cannot survive on instinct alone.

Cool Math Games Mini Metro

The version hosted on Cool Math Games Mini Metro runs the browser build directly. You do not need to download anything. The gameplay is identical to the standalone paid version in terms of mechanics and level progression. Performance can be slightly inconsistent depending on your browser. Chrome handles it fine. Firefox sometimes stutters during the late-game rush when there are twelve stations all demanding attention at once. I switched to Chrome for longer sessions and lost less time to frame drops. To play it, go to the Cool Math Games website, search for Mini Metro, and click play. The browser loads the game. Nothing else required.

How to Actually Play It Well

Start by laying down your first line before any other thought occurs to you. The early game gives you generous time to think. Use that time poorly and you will regret it later. Draw lines in this order: one line per color group, then add complexity from there. Do not combine two colors into one line just because it looks efficient. A single line carrying two colors creates a bottleneck when passengers need to transfer. You will watch your score drop while you figure out why. The train speed is constant. Adding more trains on a line increases frequency, not speed. That distinction matters more than people realize. In a dense late-game map where stations are clustered close together, running three short lines beats one long slow line every single time. Short lines cycle faster. Passengers board, the train returns, and the station empties before the queue gets dangerous.

Here is a specific edge case that caught me off guard on my third week of playing. The game generates diamond-shaped stations that require a diamond-colored train. Square stations need square trains. The color and shape of the train are determined by the line you assign it. I kept trying to route diamond passengers onto a blue square train because the blue line happened to pass near their station. The game refused to pick them up. The workaround was simple: create a dedicated diamond line, or change the existing line's shape by adding a station of the matching shape somewhere on that line. It sounds obvious now. I died to it three times before it clicked.

Common Pitfalls

The biggest mistake beginners make is creating overlapping lines. When two lines share stations, passengers sometimes board the wrong one. They ride past their destination and you lose time waiting for the next train. Keep lines separate until the late game forces you to merge them, and even then, only merge when you have no choice. Another thing nobody talks about: the branching point. When a line splits into two branches, the game sends half the train to each branch. This halves your frequency on both branches. If you are running a single train and the line splits, each branch effectively gets a train every two cycles instead of one every cycle. This is why splitting a line is dangerous in the mid-to-late game. If you must split, add a second train to the line first. The shapes matter more than colors. Colors are cosmetic. Shapes are functional. A player might obsess over keeping all red lines separate while ignoring the fact that their yellow line has a square station sitting next to a diamond station with no way to serve both without crossing lines. Prioritize shape management over color management. Your score will reflect it.

Score Optimization

Your score is based on passengers delivered per minute. Longer games with more passengers equal higher scores. The game does not end until a station fills up, so survival and efficiency are the same goal. Do not build elaborate networks that look impressive and deliver nothing. Build small, fast, reliable loops. A clean two-train system servicing eight stations consistently will outscore a messy four-train web servicing twelve stations that occasionally collapses under pressure. I reached a personal best of around 7,500 passengers on a standard map by sticking to one principle: never add a train unless you have a clear reason it will reduce backlog at a specific station. Adding a train for comfort is how you drown in your own infrastructure.

Limitations of the Browser Version

The browser version on Cool Math Games Mini Metro has some real constraints. There is no cloud save integration. If your browser clears its cache or you switch computers, your progress resets. I lost a solid hour of a running session once because I cleaned my browsing data without realizing the game stored progress locally. Save often if you can find a save mechanism, or just accept that you are grinding for a personal best each session. Input latency is slightly higher than the desktop version. When you are drawing lines in the final seconds before a station fills, that extra half-second of response time can cost you. It is measurable. I timed it. On average it is around 80 to 120 milliseconds of additional lag compared to the native version. Not game-breaking, but noticeable when you are drawing a line by hand under pressure. If you want the full experience without these compromises, the standalone version from Steam or the app stores removes all of this. It costs real money. The browser version is free. Pick your trade-off.