fmsave
Read your Football Manager 26 saves from disk into Python records, DataFrames, CSV and JSON.
Documentation: guides and the full reference.
Install
fmsave needs Python 3.12 or newer.
uvx fmsave info path/to/career.fm # try it without installing
pip install fmsave
pip install "fmsave[pandas]" # adds Table.to_pandas()
Quickstart
import fmsave
with fmsave.open("career.fm") as career_save:
my_club = career_save.managed_clubs()[0] # empty when you are between jobs
squad = career_save.players().where(club_uid=my_club.club_uid)
for player in squad.sorted_by(lambda player: player.ability.current, reverse=True)[:5]:
print(player.name, player.age, player.ability.current, player.attributes.finishing)
# "Alex Example" 24 148 16
squad_frame = squad.to_pandas() # needs fmsave[pandas]
squad.write_csv("squad.csv")
A player carries his names, birth date and age, nationality, club, height, positions, all 24 attributes, the eight personality attributes, current and potential ability, reputation, transfer value, condition, traits, his contract and any unserved ban. Records and tables are immutable and keep working after the save is closed.
Each reader returns a Table: where(...), filter(...), sorted_by(...), find(name=...),
by_uid(...), by_id(...) and coverage, plus to_dicts(), to_columns(), to_pandas(),
to_polars(), write_csv(...), write_json(...) and write_jsonl(...).
What else it reads
Twenty-six readers in all, each returning a Table of records:
- People:
players(),contracts(),suspensions(),staff(),staff_lists() - Clubs:
clubs(),managed_clubs(),finances(),sponsorships(),facilities(),stadiums(),affiliates(),job_vacancies() - Competitions:
stages(),competitions(),fixtures(),league_tables(),competition_rules(),transfer_windows(),player_match_stats() - Injuries:
injury_types(),injuries() - Your own club's work, which only the club you manage stores:
training(),mentoring(),tactics(),set_pieces()
Every field is either verified against the game or unconfirmed; ask with
fmsave.field_status(fmsave.Player, "contract.wage"). Values come from the save as stored, a value
fmsave cannot read is None rather than a guess, and money is kept in the unit the game stores it
in, which is not the currency it displays.
Each reader also measures what it decoded against loose bounds drawn from a couple of careers. A
save unlike them can miss one and still be read perfectly well, so a missed bound is a warning and
you get the table anyway. Pass strict=True to fmsave.open to have one raise instead.
What it cannot read
- Names the game renders from its own installed database. Competitions, leagues, nations,
cities and all but a couple of hundred grounds. fmsave ships none of these and reads nothing from
your game install. Competitions carry
database_id, the id every outside name source is keyed on, so you can supply your own map. See Competition names. - Links the save does not store, such as which competition a rules block belongs to, or which ground a club plays at. Worked out from the fixture calendar where possible, left empty where not.
- Meanings for numbers the game never displayed, such as staff job titles or the settings inside a tactic. These come back as raw numbers rather than as labels fmsave guessed at.
- What the save keeps only in part or not at all: scores for about three quarters of a career's matches, injuries older than about two years, and today's availability, line-ups, staff attribute values, card counts, club debt and asking prices.
Competition names
competition_names = fmsave.read_competition_names("competition-names.csv")
with fmsave.open("career.fm", competition_names=competition_names) as career_save:
for competition in career_save.competitions():
print(competition.database_id, competition.name) # 12345 "Example League"
The file is UTF-8, two columns, database_id then name; a leading header row is skipped. Any
mapping of database id to name works too. Without a map, name and every denormalised
competition_name is None. About one competition in ten carries no database id and can never be
named, and one the game created during a career carries an id no outside source holds.
Command line
fmsave info career.fm
fmsave export career.fm players --managed-club -o squad.csv
fmsave export career.fm players --nation 7 --columns name,age,club_name,contract_wage
fmsave validate career.fm --json
export writes any of the twenty-six tables as CSV, JSON or JSON Lines, and needs a scope:
--club, --managed-club, --competition, --nation or --all. Nested groups flatten to
contract_wage-style columns and a coded value gives a label column plus a _code column, so JSON
is the lossless format. --all is explicit and is for local analysis of your own single-player
save. validate runs every reader and reports its checks, counts and coverage, holding no names,
uids or text from the save, so it is safe to paste into an issue.
Where saves live
- macOS:
~/Library/Application Support/Sports Interactive/Football Manager 26/games/ - Windows: usually
Documents\Sports Interactive\Football Manager 26\games\ - Steam Cloud and other stores may keep saves somewhere else.
If the game is running, copy the save and read the copy.
Safety
fmsave is read-only. It never modifies saves, makes no network connections, and does not read game memory. Local single-player analysis is supported. Using hidden data to gain an advantage in a shared online career may break platform or community rules.
Support
fmsave is a hobby project, maintained on a best-effort basis. Report problems through GitHub issues. Never attach a save file; maintainers will not request or accept one. See CONTRIBUTING.md for how to report a wrong value without sharing real data. To request removal of any content, open an issue with the rights request form.
Disclaimer
fmsave is an unofficial fan project. It is not affiliated with, endorsed by, or sponsored by Sports Interactive or SEGA. Football Manager, Sports Interactive and SEGA are trademarks or registered trademarks of their respective owners.
License
MIT. See LICENSE.
Release files for fmsave 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fmsave-0.4.2.tar.gz | 351.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fmsave-0.4.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 744.6 kB
Release files / fmsave-0.4.2.tar.gz
| Download URL | fmsave-0.4.2.tar.gz |
|---|---|
| Size | 351.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c553a5ae255f8c9a74d8d478744e0d030ab93e6b5fde8f861fe8098c5265228
|
|
BLAKE2b-256 checksum How to use checksums |
7edc52a3da0a32f82c40ede9a94c023addfc923af0c0201e63423f6079f5577f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency logRelease files / fmsave-0.4.2-py3-none-any.whl
| Download URL | fmsave-0.4.2-py3-none-any.whl |
|---|---|
| Size | 393.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
58fe24b2e17da0e60e65f8c2dc0c51de2a505f097a275dde31a48de4030eb822
|
|
BLAKE2b-256 checksum How to use checksums |
109caf9765f906fe5a17aceecc885dc52d94ce005ce14c1c4fe88d315a1dc460
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency log