The config_default_image module allows you to set a default image for fields that can be deployed with configuration. It stores the image's file path in configuration, rather than a content ID, ensuring your default images work correctly when deploying configuration between environments.
Image field formatter allowing to set a default image deployable through config management. It stores a file path into config, instead of a content uuid.
This addresses the problem that the core default image feature uses a file content. If you use config management (drush cex/cim...) you will deploy the config but not the content, so the default image wouldn't work in production.
A blog post about this problem: https://www.58bits.com/blog/2016/04/13/synchronizing-default-images-imag...
Ask your assistant about Config default image
Check compatibility with your Drupal and PHP version, maintenance and security coverage, from current release data. How it works
Depends on
Dependencies of the latest stable release
No dependencies recorded for this project.
Required by
Tracked projects that depend on this one
No tracked projects depend on this one yet.
Activity
Release Timeline
Releases
| Version | Type | Core | PHP | Release date | |
|---|---|---|---|---|---|
| 8.x-2.0-beta7 | Pre-release | 8–11 | Apr 30, 2026 | ||
| 8.x-2.0-beta6 | Pre-release | 8–9 | Apr 16, 2026 | ||
| 8.x-2.0-beta5 | Pre-release | 8–11 | Dec 2, 2025 | ||
| 8.x-2.0-beta4 | Pre-release | 8–11 | Oct 30, 2025 | ||
| 8.x-2.0-beta3 | Pre-release | 8–11 | Nov 5, 2024 |