WordPress has announced that it is reevaluating its plan to automatically generate WebP images due to strong opposition from the community. The organization will thoroughly research the suggestions from WordPress users to make a more informed decision moving forward.
## Enabling WebP by Default
Initially, WordPress proposed a feature to generate multiple versions of every uploaded image, including WebP formats. The aim was to help publishers easily upload images and benefit from optimized WebP versions that reduce file size and enhance website performance.
However, concerns emerged about the potential for some sites to quickly exhaust their disk space due to the creation of additional images. Some members of the WordPress community suggested that the feature should be off by default and not automatically activated.
## Clash With WordPress Design Goals
The idea of shipping the WebP feature in a default-off state conflicts with the WordPress philosophy of “Decisions, not Options.” This principle emphasizes delivering products that work out of the box with minimal configuration.
WordPress outlines its philosophy with five key design goals:
1. Functional Out of the Box
2. Designed for the Majority of Users
3. Decisions, Not Options (Developers Make Decisions on Behalf of Users)
4. WordPress Core Features Must be Needed by 80% of Users
5. Simplify All Tasks
The “Decisions, Not Options” philosophy was specifically cited to justify the WebP feature being default to “on” without a user interface to turn it off. This philosophy states that developers should make smart design decisions and avoid burdening users with technical choices.
The idea of deploying a potentially disruptive feature without an easy way to deactivate it raised concerns throughout the WordPress ecosystem.
## Opposition from the WordPress Community
The proposal received passionate opposition from the community. Many were alarmed by the risk of running out of disk space, leading to non-functional websites or significant costs to purchase more storage from web hosts.
## WordPress Announces it is Reassessing WebP Feature Deployment
Adam Silverstein, a WordPress core developer, acknowledged these concerns and announced that the next step would be to reassess the proposal with more agreeable options. He pledged to conduct additional data-driven research and reconsider the approach to enabling WebP by default.
The statement clarified that they would investigate the disk storage impact of creating additional WebP images and concerns about compatibility with other functions such as email clients, RSS readers, and lazy loading.
After completing this research, WordPress will reassess whether the WebP feature should be on or off by default and consider a user interface to toggle the feature easily.
## WordPress Community Response
The news of reassessment was met with overwhelmingly positive feedback from the WordPress community. Many appreciated the careful and thoughtful approach to ensure that WordPress remains forward-thinking and competitive in the content management system space.
Overall, the decision to reassess the impact of the WebP proposal demonstrates the WordPress ecosystem’s effectiveness in collaboratively reaching a thoughtful decision that considers the potential impact on publishers.
## Citation
### Read the Official WordPress Announcement
Follow-up on WebP by Default Proposal
