Skip to main content

fmsave

Read your Football Manager 26 saves from disk into Python records, DataFrames, CSV and JSON.

Documentation: guides and the full reference. Release notes cover each release.

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 52 attributes, the 8 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. Use uid for joins within a save and unique_id to match database people or clubs across careers; created people can reuse deleted people's IDs.

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

28 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(), player_season_stats(), player_season_history()
  • 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.

Reader checks test completeness, joins and expected ranges. A failed check warns and returns the table; strict=True raises instead. Structural failures raise in either mode. See Trusting a number before relying on a result.

What it cannot read

  • Names the game renders from its own installed database. Competitions, leagues, nations, cities and most 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.
  • Partial history and unsupported fields: match-score coverage that varies by save, older injuries, and today's availability, line-ups, staff attribute values, 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, 2 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. Competitions without a database id cannot use this map; those created during a career may have no entry in an outside name source.

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 27 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. Do not attach or link a save file in an issue. To share a save, email a link to the address on my GitHub profile. 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.

Metadata

Release files for fmsave 0.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fmsave 0.6.0
File Size Uploaded Provenance
fmsave-0.6.0.tar.gz 404.9 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for fmsave 0.6.0
File Interpreter ABI Platform
fmsave-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 855.5 kB

Release files / fmsave-0.6.0.tar.gz

Download URL fmsave-0.6.0.tar.gz
Size 404.9 kB
Tags Source
SHA-256 checksum
How to use checksums
0d54fa3689a80ed3e3d5b7dcd99573c0d3198ebe61ac73420f2fc6c856ba0b32
BLAKE2b-256 checksum
How to use checksums
9afed9ed282a9024805455ed8a2cd5cbb8921e8f60140303cf8a7f7944746403
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 Oct 25, 2026.

Transparency log

Release files / fmsave-0.6.0-py3-none-any.whl

Download URL fmsave-0.6.0-py3-none-any.whl
Size 450.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f983e35952a9365b7e95b87a7efd9c892e5e7d3be041f0eb07b143dab868c901
BLAKE2b-256 checksum
How to use checksums
eca657edfb06ac0e2ca7c64073ab4daefedbe9ed13a9f7c080eb580ebf5f1ffb
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 Oct 25, 2026.

Transparency log

Security for fmsave 0.6.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for fmsave-0.6.0.tar.gz

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 Oct 25, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page