Repository navigation
[web] Support content-hashed static assets in AssetManifest (--web-content-hash) #191915
Description
Summary
Part of umbrella issue #149031.
Support content-hashing static assets (images, fonts, JSON configs, shaders) placed under assets/ when building Flutter Web with --web-content-hash.
Scope & Requirements
- Compute SHA-256 content hashes for asset files during
flutter build web --web-content-hash. - Rename physical files in
build/web/assets/to include content hashes (e.g.assets/images/dash.a1b2c3d4.png). - Update the target path mappings in
AssetManifest.bin/AssetManifest.jsonandFontManifest.json. - Keep asset lookup keys in user Dart code unchanged (
rootBundle.load('assets/images/dash.png')). - Enable long-term
Cache-Control: max-age=31536000, immutablecaching on all static assets underassets/.
Activity
feat(web): support --web-content-hash for physical static assets
fix(web): hide --web-content-hash until content hashing is complete (f…
feat(web): support --web-content-hash for physical static assets (flu…
feat(web): resolve raw asset keys via content-hashed manifests and un…
github-actions commentedon Oct 7, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.