The 2D match engine
The picture stays 2D. The posts say newer match logic came across from the PC edition.
The picture stays 2D. The logic is what they say moved. SEGA's 5 November feature blog calls the match engine in Football Manager 27 Mobile the most advanced 2D engine in the mobile series. It brings across the latest match logic and keeps the familiar 2D presentation. The blog's words for the result are smoother, more powerful, and more authentic. Those are adjectives. The checkable claim is the 2D picture plus the newer match logic. The FAQ on that same page, and Zachary Whyte's community FAQ, say the 2D engine was brought over from the PC version of this season. That is the link to the computer game. It is an engine link, not a save link and not a store link. The phone game is still the Netflix one. The PC split stays in force.

The 2D match view with the score bar. Official screenshot, SEGA feature blog, 5 November 2026.
Between the highlights
Both FAQs say that between the on-pitch moments you get additional statistics, graphs, and more, so you can read your side and the opposition before the next tactical decision. The posts do not name every graph. Expected Goals is the statistic they do name. It is on its own page because it also shows outside the match: where Expected Goals shows. The Out Now post calls the same block an updated match engine, with real-time statistics like Expected Goals. "Like" means Expected Goals is the example they chose, not a promise of a full stat pack this site will list.
What you do in a match
Start a match or a highlight. Watch the 2D view. When the action breaks, look for the extra numbers and graphs the FAQ described. If you want the one named metric, look for Expected Goals in the match, then later in a league table and in a post-match report. The blog says that metric is there so you can tell whether the team created the chances, or whether the forwards had a bad day in front of goal. That is the use they published. It is not a target number. The screenshots on the feature blog are marked as a development build with localisation still in progress. A scoreline or a player name in those frames is a frame, not a published rule.
What is not in the engine posts
No frame rate. No camera count. No claim that every PC animation is on the phone. No claim that the 2D view can be switched to 3D. If a setting for that exists, the posts this site used do not mention it, so it is not written here.
| Source | What it says about match day |
|---|---|
| Feature blog | Most advanced 2D engine in the mobile series; latest match logic; 2D picture kept |
| Blog FAQ and community FAQ | 2D engine brought over from the PC version |
| Both FAQs | Extra stats and graphs between on-pitch moments |
| Out Now post | Updated engine, real-time stats, Expected Goals as the example |
Feature blog. Community FAQ. Out Now.
Picture stays 2D
Hold the adjectives as adjectives. Hold the 2D line as the line you can check. A shared engine does not smuggle a PC career onto the phone.
During the 2D view
Do not turn the reading aid into a score you must hit. A name in a frame is not a player this site will repeat.
Left out of the engine posts
If a setting for that exists, the posts this site used do not mention it, so it is not written here. Absence is not a dare to invent a setting the posts did not mention. The 2D picture is the picture they said they kept.
What a carried save does with it
The engine arrives with the update, so a career you carried into this season sits inside it. You do not choose it, and there is no switch in the posts that turns the old match logic back on. What that means in practice is that the first match on a carried save is worth watching rather than skipping. The setups you brought across are yours, and the logic running them is this season's. Those two things have not been in the same room before. A tactic that produced a certain kind of chance last season will still produce chances, but the picture of how those chances arrive is the new engine's picture. The screenshots on the feature blog are marked as a development build, and the blog says localisation was still in progress when they were taken. That matters for one narrow reason: a name or a scoreline in a frame is a moment in a development build, not a published description of the engine. The engine claims are about the 2D picture, the match logic brought across from the computer game, and the statistics between the moments. Everything else in those frames is decoration.