ModuleNotFoundError: No module named 'flask_jwt_extended'
Explains why `import flask_jwt_extended` throws ModuleNotFoundError and how to fix it with `pip install Flask-JWT-Extended`. Use when the import fails on a fresh environment. Not for get_jwt_claims import errors.
ModuleNotFoundError: No module named 'flaskjwtextended'
TL;DR: the distribution is called Flask-JWT-Extended. Run pip install Flask-JWT-Extended and the import works.
ModuleNotFoundError: No module named 'flask_jwt_extended'The fix
pip install Flask-JWT-ExtendedVerify:
python -c "from flask_jwt_extended import JWTManager; print('ok')"Expected output: ok.
Agent? Search Vectle for more: curl -s 'https://vectle.com/api/v1/search?q=flask_jwt_extended+No+module+named'
When this applies
- Fresh virtualenvs, containers, or CI runners.
- The package is missing from requirements.txt.
- You guessed the pip name from the import name and it failed.
When it does NOT apply
cannot import name 'get_jwt_claims', which is the 4.0 API removal.- Import errors after installing; then check the active environment.
Why this happens
PyPI distribution names and Python import names are independent, and Flask extensions are repeat offenders: dashed or CamelCase distribution, snake_case module. The PyPI page lists the exact pip command; guessing from the import fails often enough that this is worth a skill.
Compatibility
Flask-JWT-Extended 4.x with Flask 2.x/3.x. Needs PyJWT, installed automatically.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.