Skip to content
DoCodeHereDeveloper tools and services

Code editors and AI coding tools · Researched comparison

Best Python Static Type Checkers in 2026

mypy is the first pick for most teams because it is the reference implementation of PEP 484 and has the widest plugin and CI support. Pyright suits teams that want fast checks and strong editor integration through Pylance in VS Code. Pyre is a reasonable alternative for large codebases that want incremental checking and a query API. All three are free.

By · Published 22 Nov 2026

We run no ads and no affiliate links at launch. The order of a list follows our published method.

Prices are the starting prices vendors list publicly. Plans change, so confirm the current price on the vendor page before you buy.

Key takeaways

ToolBest forStandout featureListed starting priceFree plan or trial
1 mypyTeams that want the reference type checker with broad plugin supportReference implementation of PEP 484Free (open source)Free plan
2 PyrightVS Code users who want fast checks and strong editor feedbackFast analysisFree (open source)Free plan
3 PyreLarge codebases that need incremental checks and a query APIIncremental checking on big reposFree (open source)Free plan
4 tyDevelopers who want a very fast checker from the Ruff teamVery fast analysisFree (open source)Free plan
5 PyCharm type checkerPyCharm users who want built-in inspection without extra setupBuilt into the IDESee vendor pricing pageFree trial (30 days)
6 BasedpyrightPyright users who want stricter defaults and extra rulesStricter defaults than PyrightFree (open source)Free plan

How we picked

We compared tools on fit for static type checking of Python, supported platforms, licence and price, editor and CI integration, strictness configuration, and known limits such as speed and coverage of newer typing features. Sources are vendor pages, official documentation and project repositories. We did not run benchmarks. Prices and edition details change, so confirm them on the vendor site before you commit.

01

mypy

Best for: Teams that want the reference type checker with broad plugin support

mypy is the original static type checker for Python and the project that defined the PEP 484 type hint syntax. It runs from the command line on Linux, macOS and Windows, and integrates with most editors through language server plugins. It reads type stubs from typeshed and supports third-party stub packages.

Configuration lives in a mypy.ini, setup.cfg or pyproject.toml file, where you set strictness flags such as disallow_untyped_defs and warn_return_any. The plugin system covers frameworks like Django and SQLAlchemy, which plain type hints cannot fully describe. It is released under the MIT licence.

The main limit is speed. On very large codebases mypy can take minutes per run, and incremental caching only partly offsets this. Teams that want the fastest feedback loop in the editor may prefer Pyright. Teams that depend on framework plugins or want the most widely documented behavior should start with mypy.

Pros

  • Reference implementation of PEP 484
  • large plugin ecosystem and wide CI support

Cons

  • Slower on large codebases
  • strict mode needs configuration

Price: Free (open source), as listed by the vendor (mypy website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: slower on large codebases.

Verdict. A sensible pick for teams that want the reference type checker with broad plugin support.

02

Pyright

Best for: VS Code users who want fast checks and strong editor feedback

Pyright is a static type checker from Microsoft, written in TypeScript and distributed as an npm package and a Python wrapper. It runs on any platform with Node.js or through the pip-installable pyright package. It powers Pylance, the default Python language server in VS Code.

Pyright supports the full PEP 484 type system plus newer features such as PEP 695 type parameter syntax. It offers configurable strictness through pyrightconfig.json or pyproject.toml, with basic, standard and strict modes. It can also run in watch mode during development. The source is on GitHub under the MIT licence.

Because Pyright aims to match the typing spec rather than mypy's exact behavior, error output can differ on the same code. Projects migrating from mypy may see new errors or fewer. There is no plugin system, so framework-specific inference that mypy plugins provide is not available. It is the best fit for VS Code users and teams that want fast CI checks.

Pros

  • Fast analysis
  • deep VS Code integration through Pylance

Cons

  • Defaults differ from mypy
  • some mypy plugins have no equivalent

Price: Free (open source), as listed by the vendor (Pyright website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: defaults differ from mypy.

Verdict. A sensible pick for VS Code users who want fast checks and strong editor feedback.

03

Pyre

Best for: Large codebases that need incremental checks and a query API

Pyre is a static type checker built by Meta and released under the MIT licence. It runs on Linux and macOS and is designed for large, evolving codebases. It keeps a persistent server process so repeated checks are incremental rather than full re-analyses.

Pyre includes a query API that answers questions about types and call graphs, which teams use to build code intelligence and refactoring tools. Configuration lives in a .pyre_configuration file. Strictness is controlled per-directory and per-file, so a team can adopt types gradually without failing the whole build.

The tradeoff is operational weight. Pyre needs a running server and more setup than a single command-line tool, and it does not run natively on Windows. It has fewer third-party framework plugins than mypy. Small projects and solo developers will get more value from mypy or Pyright. Large monorepos with dedicated tooling staff are the target audience.

Pros

  • Incremental checking on big repos
  • query API for code intelligence

Cons

  • Setup is heavier
  • fewer framework plugins than mypy

Price: Free (open source), as listed by the vendor (Pyre website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: setup is heavier.

Verdict. A sensible pick for large codebases that need incremental checks and a query API.

04

ty

Best for: Developers who want a very fast checker from the Ruff team

ty is a type checker from Astral, the team behind the Ruff linter and uv package manager. It is written in Rust and distributed as a standalone binary, so it runs on Linux, macOS and Windows without a Python runtime dependency for the checker itself. The project is open source.

ty focuses on speed and a small configuration surface. It reads standard type hints and aims to match established checker behavior where the typing spec is clear. Because it is newer, some advanced typing features and framework-specific inference may lag behind mypy and Pyright. Its diagnostics and defaults can change between releases.

For teams already using Ruff and uv, ty fits the same workflow and install style. It is a good choice for fast pre-commit checks and editor feedback. Teams that depend on stable, long-documented error output or mypy plugins should treat ty as a secondary check until its coverage matures. Check the repository for current feature status before adopting it in CI.

Pros

  • Very fast analysis
  • simple single-binary install

Cons

  • Newer project with less mature coverage
  • behavior still changing

Price: Free (open source), as listed by the vendor (ty website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: newer project with less mature coverage.

Verdict. A sensible pick for developers who want a very fast checker from the Ruff team.

05

PyCharm type checker

Best for: PyCharm users who want built-in inspection without extra setup

JetBrains PyCharm includes a built-in type checker that runs as part of its code inspections. It highlights type errors in the editor and supports type hints, generics and stubs. Because it ships with the IDE, there is no separate command-line setup for day-to-day work.

PyCharm has a free Community edition and paid Professional edition; the built-in type inspection is part of the IDE rather than a standalone product. For CI, JetBrains does not position the IDE inspection as a headless checker, so teams typically pair it with mypy or Pyright in the pipeline. Pricing changes, so confirm current editions and prices on the vendor page.

This option suits developers who already work in PyCharm and want immediate feedback while editing. It is not a replacement for a command-line checker in CI, and it does not run outside the IDE. Teams on VS Code or Neovim should use Pyright or mypy instead.

Pros

  • Built into the IDE
  • no separate install or config file

Cons

  • Tied to PyCharm
  • not a standalone CI tool

Price: See vendor pricing page, as listed by the vendor (PyCharm type checker website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: tied to PyCharm.

Verdict. A sensible pick for pyCharm users who want built-in inspection without extra setup.

06

Basedpyright

Best for: Pyright users who want stricter defaults and extra rules

Basedpyright is a fork of Pyright that keeps the same engine but changes defaults and adds checks. It runs wherever Pyright runs and installs through npm or pip. It is open source and maintained on GitHub.

The fork enables stricter default settings, adds rules such as reporting unannotated functions, and offers a baseline mode for suppressing existing errors so a team can adopt it gradually. It also provides its own VS Code extension. Because it tracks Pyright, it inherits fast analysis and broad typing-spec coverage.

The tradeoff is divergence. Error output differs from upstream Pyright, so documentation and CI configs written for Pyright may need adjustment. The community is smaller, and fixes depend on the fork maintainers. Teams that want Pyright's speed with stricter defaults should evaluate it; teams that want the most widely used tool should stay on Pyright itself.

Pros

  • Stricter defaults than Pyright
  • adds rules Pyright lacks

Cons

  • Diverges from Pyright behavior
  • smaller community

Price: Free (open source), as listed by the vendor (Basedpyright website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: diverges from Pyright behavior.

Verdict. A sensible pick for pyright users who want stricter defaults and extra rules.

Who should use what

Teams starting with type hints should use mypy for its documentation and plugin support. VS Code users who want fast editor feedback should use Pyright or its stricter fork, Basedpyright. Large monorepos with dedicated tooling staff should evaluate Pyre for incremental checks and its query API. Developers already using Ruff and uv can try ty for fast checks, keeping mypy or Pyright as the primary gate.

What to check before you buy

FAQ

Are Python static type checkers free?

mypy, Pyright, Pyre, ty and Basedpyright are free and open source. PyCharm's built-in type inspection is part of the IDE, which has a free Community edition and a paid Professional edition. Confirm current editions and prices on the vendor page.

Which checker is fastest?

Pyright and ty are designed for fast analysis, and Pyright is widely used for editor feedback. mypy is generally slower on large codebases, and Pyre uses incremental server-based checks to reduce repeat run time. We did not run benchmarks, so test speed on your own repository.

Can I use more than one type checker?

Yes. Some teams run mypy in CI and Pyright in the editor, or add ty as a fast pre-commit check. Error output differs between tools, so pick one as the primary gate and treat others as secondary. Running several checkers adds CI time.

Do type checkers catch all bugs?

No. Static type checkers find type mismatches and some logic errors, but they do not replace tests. Strictness settings control how many errors are reported.

Is it safe to paste code into online type checkers?

Avoid it. Source code can contain secrets, internal URLs and proprietary logic. Run type checkers locally or in CI instead. Prefer tools that execute on your machine, and do not upload production code to third-party web pages.

Sources we checked

  1. mypy (official site)
  2. Basedpyright (official site)
  3. Pyre (official site)
  4. Basedpyright (official site)
  5. PyCharm type checker (official site)
  6. Basedpyright (official site)

Change log. First published 22 Nov 2026.