THE MATCHDAY ANSWER
Custom databases
Identify what the download contains, confirm its edition and required base database, then test it alone in a new career. Verify a specific advertised change inside the game before starting your long-term save. Keep an untouched copy of your working files and career.
What is confirmed, and what is advice?
The linked editor discussions and bug report concern FM26. They reveal useful failure categories but do not establish FM27 bugs, universal folder paths or automatic compatibility. The workflow below is a reversible diagnostic plan; confirm FM27 support with each file’s author.
Reviewed 4 November 2026. Match examples are hypothetical. The checks and suggested adjustments are Touchline FM editorial advice, not guaranteed results or engine formulas.
Start with these three decisions
- Classify the file: career, editor changes, tactic or graphics pack.
- Check edition, base database, author requirements and the active user-data location.
- Test one compatible file in a fresh career and verify a visible change before combining files.
Know what you downloaded
A saved career and an editor data file solve different problems. A career already contains a simulated world. A pre-game change file is intended to modify the setup of a new world. The older editor discussion highlights confusion between that additional file and the base database selector. Do not expect a custom file to appear as an entirely new official database version.
An extension alone is not a complete installation guide. Different FM resources may share a container extension while performing different jobs. Read the author’s description and unpack an archive only into a separate working folder first. Identify the actual payload before copying anything into game folders. Renaming an incompatible resource does not convert it into the correct format.
Source notes: SI forum: problems with the pre-game editor
Check the compatibility contract
Before troubleshooting a missing file, record the game edition, installed game build, editor version, selected base database and the file’s stated requirements. Compatibility should be stated by its author or demonstrated in a controlled test. A successful FM26 installation does not prove that the same data file works with FM27, even when its name looks similar.
Check whether the package requires other files, a specific start date or particular leagues. Preserve those dependencies during the isolated test; “one file” means the smallest supported package, not arbitrarily removing a required component. If the author has not supplied FM27 instructions, ask for compatibility information rather than treating a failed load as proof that your game installation is broken.
Find the active folder, not a familiar folder
Use the game’s current user-data location and the author’s instructions as the starting point. macOS and Windows can have several similar Sports Interactive folders, and custom locations or cloud-synchronised Documents folders can add another copy. The place where the game is installed is not necessarily the place where it reads user-created content.
The historical FM26 report includes files not appearing despite users trying folders and reinstalls. That is a reason to establish a minimal reproduction, not a reason to recommend reinstalling first. Confirm the destination you are using, look for accidental nested folders after extraction and make sure the file is locally available. Work on copies; do not delete whole user-data folders to test a single resource.
Source notes: SI tracker: editor data not appearing
Separate four different failures
“It does not work” can mean the game never lists the file, the change is not applied, a competition cannot start or the season fails later. Locate the first failing step before changing the installation. Use this table to choose the next check, keeping your working career outside the experiment.
| Failure | First check | Evidence to retain |
|---|---|---|
| File not listed | Correct payload, edition and active user-data folder | Author instructions and actual destination |
| Listed but changes absent | Selected change files and base database in a new career | One specific player or club change |
| Nation or competition unavailable | Required dependencies and verified rules for this setup | Selected nations, start date and validation message |
| Career starts but later breaks | Fixtures, season transitions and compatibility conflicts | Last working test date and repeatable steps |
Test the smallest supported setup
Create a temporary career with the supported package and a deliberately small selection of leagues. Keep the official base database and start conditions consistent with the author’s requirements. Check an advertised change by name or identity, then inspect the relevant club, competition or rule. A file appearing in the selector is only the first checkpoint.
Add your other compatible packages back in controlled steps. If a problem returns, repeat the smallest failing combination rather than guessing which file “wins.” Two files changing the same competition or registration structure deserve particular attention. Do not assume a universal filename order resolves every conflict. Preserve a note of the combination that worked so future updates do not erase your baseline.
Test the season, then start the story
For competition changes, review scheduled fixtures and simulate a test through the relevant season transition. Check promotion, relegation and qualification paths that the package claims to modify. A successful rules check in an editor is useful, but your intended combination still needs an in-game test. One completed season is a checkpoint, not a guarantee for a twenty-year career.
Pre-game changes normally require a new career; do not promise that adding a file rewrites an existing save. If you want an already simulated world, use the separate five- or ten-year career downloads instead. Savegame Scout reads supported career files locally but does not install editor packages or repair competition rules. These are different tasks, so choose the route that matches the result you want.
Send a report somebody can reproduce
Include the exact edition and builds, base database, package version, selected files, nations, start date and the first visible failure. Explain the expected change and the observed result. Mention whether the smallest supported setup worked alone. This gives the author or SI a much stronger starting point than a screenshot of an empty selector without context.
Share a minimal test file only through the appropriate channel when requested, and review what it contains first. A public help thread is not the place to expose private career data unnecessarily. Keep the working original untouched while support investigates. Your final installation note should say exactly which combination passed, rather than claiming that every FM27 custom database is now compatible.
EVIDENCE BEHIND THE ADVICE
Sources & edition notes
Official FM27 announcements establish current changes. Earlier-edition sources provide background. Community discussions identify questions and experiences; being hosted on SI’s forum does not make them official confirmation. Our recommendations are labelled as advice.
- FM26 community discussionSI forum: problems with the pre-game editor
An older discussion distinguishes a base database from an additional file of edits. Interface labels and file compatibility must be checked for the installed edition.
- FM26 bug report · July 2026SI tracker: editor data not appearing
Historical reports include missing edits and requests for reproducible files. They demonstrate why folder, build and reproduction checks matter, without establishing a current FM27 bug.