Nginx still refuses dark mode for error pages a year after community vote — 579 to 59 in favor

In early 2025, the upstream Nginx web server rejected a proposal to add dark mode support for its default error pages. The developers argued that the error pages should remain simple and that adding an extra HTML tag for dark mode styling was unnecessary. The decision sparked a wave of public backlash, as many users consider dark mode a standard feature that significantly improves the user experience, especially given the widespread adoption of dark themes in modern operating systems and browsers.

In response to the criticism, an employee of F5 — the company that owns Nginx — initiated a public discussion poll. The poll asked users whether they liked or disliked the idea of native dark mode support for error pages. The results were overwhelming: 579 thumbs up in favor versus only 59 thumbs down. With roughly 600 positive reactions, the supporters of the feature appeared to have won by a landslide.

Despite this clear mandate, progress stalled. In June 2025, a follow-up question was posted asking for conclusions based on the voting results, but it received no response from the upstream Nginx developers. Later, another query was made about the status of the dark mode feature for default error pages, but again, the developers remained silent.

More than a year after the initial poll, there is still no resolution or any official explanation for why the community's strong preference was ignored. The original pull request that would add dark mode support remains untouched, with no commits or comments from the maintainers. The situation has left many users frustrated, as the feature is technically simple to implement — involving only a few lines of CSS — and would not compromise the simplicity of the error pages. The silence from the Nginx team, especially given the democratic process they initiated, has raised questions about the project's governance and responsiveness to its user base.