“Gmail will automatically respect the system default setting.”
Remember this, Gmail?
You said it in 2019 when you announced Dark Theme for Gmail on Android and iOS.
2019.
Seven years ago.
I remember. Email developers remember. Pepperidge Farm probably remembers.
And I can tell you what happened in the seven years since.
Every email client handles Dark Mode a little differently because apparently consistency would have made our jobs too easy.
But Gmail, yours earned a special name among email developers:
Forced Dark Mode.
That's right.
You're the difficult kid in the classroom.
Instead of allowing developers to provide our own Dark Mode styles, Gmail's mobile apps transform the email themselves.
And they don't even agree with each other about how to do it.
As Nicole Merlin explains in her article, Gmail finally adds the ability to opt out of forced Dark Mode, Gmail on iOS tends to invert colours, while Android applies a more selective darkening algorithm.
Her description of what this has meant for email teams is painfully accurate:
“Gmail’s mobile apps have basically redesigned every single email in Dark Mode – without asking.”
Yes.
Redesigned. Without asking.
Entire teams can spend hours designing, developing, reviewing, approving and testing an email.
Then Gmail gets it and says:
Cute. Let me try.
Background colours change.
Text colours change.
Brand colours change.
A dark logo sitting beautifully on a transparent background?
Poof.
Congratulations. Your logo is now playing hide-and-seek.
Buttons can disappear into their backgrounds. Text can lose contrast. Icons can behave unpredictably.
And for years, we tried to work with it.
Email developers tested.
We documented.
We wrote articles.
We held webinars.
We compared screenshots.
We invented increasingly ridiculous hacks.
And then we went back to our clients and coworkers and said:
Dark Mode matters.
We explained that people deliberately choose Dark Mode. We convinced designers to think beyond the beautiful Light Mode Figma file sitting in front of them.
Then we showed them the Gmail render.
Their brand colours had changed.
Their logo disappeared.
Their carefully designed colour combinations weren't so carefully designed anymore.
And somewhere in the room, somebody inevitably asked:
“Can't we just turn Dark Mode off?”
“No,” we said.
Because the recipient chose Dark Mode.
And remember, Gmail?
You told us you respected that.
When Gmail introduced Dark Theme in 2019, Google explicitly said Gmail would “automatically respect the system default setting.”
So we kept going.
Actually, don't answer that.
I don't want to know.
I personally cannot count the hours I've spent troubleshooting Gmail and finding tricks and hacks to make incredibly simple things work in an inbox.
Some of those hacks are wild.
If I used this kind of code on a website, Google, I'm fairly certain you'd send Chrome over to my house to personally confiscate my laptop.
But this is email.
So we hack. We test. We explain. We compromise.
And now it's 2026.
Seven years after telling users that Gmail would respect their system setting, you've arrived with a groundbreaking solution:
<meta name="color-scheme" content="light only">
Oh.
OH.
I have questions, Gmail.
So many questions.
This isn't hypothetical.
As Nicole's testing confirms, Gmail's iOS and Android apps now recognize light only for Gmail and Google Workspace accounts. When it's present, Gmail keeps the email in its original Light Mode design even when the device and Gmail itself are in Dark Mode.
So:
The subscriber chose Dark Mode.
Their phone is in Dark Mode.
Their Gmail interface is in Dark Mode.
And now I — the email developer — can put one line into an email and say:
Not this one, [first_name]. ☀️
Then [first_name] opens the email in bed at 11:47 p.m. and gets the visual equivalent of opening the refrigerator.
SURPRISE!
LIGHT MODE!
This is exactly the trade-off Nicole identifies: opting out “can also override the recipient’s choice.”
And that is the part I can't get past.
You actually gave email developers control.
Gmail!
The email client famous for deciding which parts of our code it does and doesn't want to support has looked at this particular line and said:
You know what? We'll allow it.
Interesting.
Very interesting.
Because what developers have wanted for years wasn't simply an OFF switch.
We wanted the ability to design Dark Mode properly.
Let us specify the colours.
Let us swap the logo.
Let us preserve brand colours where they matter.
Let us use:
@media (prefers-color-scheme: dark)
Let us create an intentional Dark Mode experience instead of reverse-engineering Gmail's colour transformations.
This is where Nicole nails it: proper prefers-color-scheme support could give us “the best of both worlds.”
Instead:
“Gmail has delivered only half a solution.”
Exactly.
Because Gmail can now understand:
Don't give this person Dark Mode.
But it still doesn't understand:
Here's the Dark Mode I specifically designed for them.
Gmail.
That is not what we meant.
Technically?
Mine.
Realistically?
My clients'.
And I don't blame them.
Imagine spending years watching Gmail change your carefully approved brand colours and being told:
“That's just what Gmail does in Dark Mode.”
Then one day your email developer walks in and says:
“Great news! I can stop it now.”
Of course they want their brand colours back.
Of course they want the email to look like the design they approved.
And there are legitimate reasons to use this new control.
Forced Dark Mode can itself create accessibility problems. Gmail's transformations can cause contrast and legibility failures. Sometimes preventing that transformation may genuinely be the safer choice.
So this isn't:
Brand good. Dark Mode bad.
It's:
Why are we being forced to choose?
Why should preserving an intentionally designed, accessible email require overriding the recipient's Dark Mode preference?
And why is that now our decision?
I'm the developer who's supposed to put this line into the template I hand to my client.
The same client I've spent years telling:
We have to account for Dark Mode because your subscribers use it.
And now:
“Good news! Gmail gave us a solution.”
“What is it?”
“We can ignore their preference.”
…
Fantastic.
Maybe [first_name] won't care.
Maybe they will.
Maybe they chose Dark Mode because that's simply how they prefer to use their phone.
Maybe they open an email at night and wonder why this one suddenly lights up their screen.
And if subscribers do notice?
Well...
It would prove something we've spent years trying to explain:
Dark Mode matters.
We'd just be learning it the hard way.
That's my biggest question.
Is light only an escape hatch while Gmail works toward proper Dark Mode support?
Because if that's what this is:
Great.
Seriously.
Forced Dark Mode has real problems. Giving developers a reliable way to prevent broken, inaccessible or brand-damaging transformations is useful.
As Nicole points out, this gives developers a meaningful new level of control.
Keep it.
But if this is the solution?
No.
Turning Dark Mode off doesn't fix Dark Mode.
It avoids it.
Even the Email Markup Consortium describes blocking forced Dark Mode as a useful quick fix while pointing straight back to the fundamental problem: the user's preference is no longer being respected.
Which brings me right back to 2019:
“Gmail will automatically respect the system default setting.”
Which one is it, Gmail?
I've been working with AI a lot lately.
Sometimes Claude decides it has completed a task when I strongly disagree that the task is, in fact, complete.
So I've developed a technique.
I give it a checklist and tell it:
Do not come back until you've checked every item.
It works surprisingly well.
So Gmail, this one's for you.
And most importantly:
We'll be here.
We've already been waiting seven years.
📩 Connect with me on LinkedIn or send a message.
With Love from Kitsilano, Vancouver — feeling much better now, thank you for asking. 😂
Annett
Founder, EmailBoutique.io
