Why SaaS Companies Struggle With Dark Mode Design and How to Fix It

Dark mode has gone from a developer preference to an expectation among professional users. Nearly every major SaaS platform now offers it, and many users treat a missing option as a red flag. Yet far more SaaS companies ship a dark theme than get it right. The reason is not a lack of effort, it […]

Dark mode has gone from a developer preference to an expectation among professional users. Nearly every major SaaS platform now offers it, and many users treat a missing option as a red flag. Yet far more SaaS companies ship a dark theme than get it right. The reason is not a lack of effort, it is that dark mode design introduces a completely different set of constraints that most teams never fully account for before launch. The result is interfaces that look sleek at first glance but create eye strain, data-visualisation errors, accessibility failures and brand erosion the moment a user spends more than a few minutes working inside them.

At Monk Creatives, we build and refine digital products from our studio in Chennai, India. Across projects for clients in finance, healthcare, hospitality and e-commerce, we have seen how a poorly considered dark theme can undo months of careful design on a light version. Getting dark mode right is not simply a matter of inverting colours. It requires a structured understanding of contrast ratios, component behaviour, colour psychology and accessibility standards, applied consistently across every screen of a product. This article walks through the specific reasons SaaS companies stumble on dark mode design and presents a practical framework for fixing each problem at its root.

Why dark mode matters more for SaaS than for most other product types

A consumer blog or brochure website may spend twenty or thirty seconds per visit. A SaaS dashboard, project management tool, analytics platform or customer support system can keep users in front of it for eight, ten or twelve hours in a single working day. The cumulative effect of poorly chosen dark colours, slightly too bright labels, a chart where the grid lines disappear, an input field that blends into the background, compounds across every one of those hours. Users do not always identify the source of their discomfort. They simply feel tired, frustrated or vaguely dissatisfied, and they attribute it to the product rather than to a specific design choice that happened months earlier in development.

There is also a brand dimension that SaaS teams overlook. Most companies invest heavily in a consistent visual identity, a logo, a colour palette, a typographic system, that is optimised for a light background. When that same palette is overlaid onto a dark surface without adaptation, the brand can look hollow, washed out or inconsistent. A brand colour chosen for vibrancy on white can become garish or illegible on near-black. Typography that looks crisp on a light canvas may feel thin and ghost-like in dark mode. These are not minor aesthetic complaints. In a market where multiple competitors offer functionally similar features, the perceived polish of an interface is a meaningful factor in user retention and willingness to upgrade.

The five design problems that break most dark mode implementations

Most dark mode failures trace back to five recurring mistakes. Understanding each one in isolation helps teams spot the symptoms in their own products.

1. Incomplete colour token systems

Teams that treat dark mode as a toggle rather than a separate theme often simply lower the brightness of every existing colour. This produces surfaces that are too dark, text that is too light and brand colours that vibrate against the background. A proper dark theme requires its own design tokens, background shades, surface shades, text primaries and text secondaries, that are defined independently and tested for visual harmony, not mechanically derived from the light palette.

2. Chart and data-visualisation failures

SaaS products frequently display charts, graphs, heat maps and tables. Dark mode breaks many of these by making grid lines, axis labels and data series invisible or visually competing. A line that was visible against a white grid can vanish against a dark one. Two data series with different hues can become indistinguishable when desaturated for dark backgrounds. This is not a theoretical concern, it directly damages the core utility of analytics-heavy products.

3. Accessibility mismatches

Contrast ratios that pass WCAG guidelines on a light background do not automatically pass on a dark one. Dark backgrounds tend to reduce the contrast of coloured text against its surface while increasing the contrast of light grey text against dark surfaces. Teams that test accessibility only in light mode are likely to ship dark-mode combinations that fail for users with low vision or colour perception differences.

4. Component state confusion

Interactive elements, buttons, links, form inputs, toggles, dropdowns, rely on subtle visual cues to communicate state. A hover effect that looks right on a light button can become invisible on its dark counterpart. Focus indicators that blend into a dark background keyboard-users dependent on assistive technology. Error messages written in red that passes on white can become unreadable on dark surfaces if the surrounding colour palette is not adjusted alongside them.

5. Brand inconsistency across themes

When a product that looks like one brand in light mode looks like a completely different, or generic, brand in dark mode, users experience a cognitive disconnect. They may not consciously notice it, but the inconsistency erodes trust. This happens when brand colours are not adapted for dark surfaces, when typography scales differently between themes, or when illustration and icon styles that were built for light backgrounds are simply placed on dark ones without redrawing.

How a proper colour system prevents most dark mode problems

The foundation of a successful dark theme is a colour system that is built for it, not retrofitted onto it. At Monk Creatives, we approach this by defining a full set of semantic tokens before any pixel work begins. These tokens map every role an colour plays in the interface, background, surface, elevated surface, primary text, secondary text, disabled text, border, divider, primary action, secondary action, success, warning, error and informational, to a specific hex or HSL value within the dark palette. That mapping then feeds directly into the component library, so every button, card, input and chart element draws from the same consistent set of values.

This approach eliminates the most common dark mode error: picking colours ad hoc for individual components. A chart designed with a specific background token will always have grid lines that contrast correctly against it, because the grid colour was chosen with that specific background in mind, not as an afterthought. Similarly, form labels and placeholder text are assigned tokens at the system level, preventing the all-too-familiar situation where placeholder text in one field is visible and in another field is invisible.

The financial services sector is a useful case study for why this matters. We developed identity systems for Vaultex and Ashutosh Finpro Services, both Chennai-based financial brands. In both projects, colour had to convey trust and security as reliably in print as it did digitally. The same principle applies when a financial SaaS product needs to display the same dashboard in both light and dark themes: the colours must communicate the same meaning in both contexts, or the interface loses its informational clarity. A brand identity built with semantic colour thinking transfers directly into a well-structured dark mode design system.

Dark mode design mistakes compared: a checklist

The table below summarises the most frequent dark mode errors alongside the correct approach. Teams can use it as a quick audit when reviewing an existing implementation or planning a new one.

Common mistakeWhy it failsCorrect approach
Pure black (#000000) as the backgroundCreates harsh contrast with text and colour elements, causing halation and eye strain on OLED and LCD displays alikeUse a very dark grey (typically #121212 or a custom near-black) that softens contrast while maintaining the dark aesthetic
Inverting the entire light paletteBrand colours, data visualisations and UI accents lose vibrancy and can become illegible; design intent is lostDefine a separate dark palette with adjusted saturation and luminance values for each brand colour and UI element
Using the same elevation system as light modeLight mode relies on shadows for depth; dark mode cannot rely on shadows alone and needs surface layering through tonal differencesBuild an elevation system based on progressively lighter surface tones for cards, modals, dropdowns and popovers
Skipping contrast testing in dark modeColours that pass WCAG ratios in light mode often fail in dark mode, especially for secondary text and placeholder contentTest every text and UI colour combination against its dark background target using the WCAG 2.1 contrast checker, aiming for AA at minimum and AAA where practical
Applying dark mode only to the main app shellEmpty states, error pages, onboarding screens, emails and help documentation remain in light mode, creating jarring transitionsExtend the dark theme to every customer-facing surface, including emails, embedded help centres and public pages, so the experience is coherent throughout
Neglecting image and illustration treatmentPhotographs and illustrations designed for a light background can look jarring or require heavy dark overlays that obscure contentProvide assets in both light and dark variants, or use CSS-based blending modes and overlays that adapt image brightness to the current theme

Accessibility is not optional in dark mode

Dark mode and accessibility are closely linked, but they are not the same thing. A dark theme can be accessible, and a light theme can fail accessibility standards. The critical point is that dark mode introduces its own set of contrast scenarios that must be tested independently. WCAG 2.1 requires a minimum contrast ratio of 4.5 to 1 for normal text and 3 to 1 for large text against their background. Those ratios are calculated from the specific combination of text colour and background colour, not from the colours in isolation.

In practice, this means that a mid-grey text colour that sits comfortably on a white background may be perfectly readable on a dark grey background or entirely invisible, depending on the exact shade of the dark background. Teams that rely on the same text colour across both themes will inevitably fail for some users in at least one of those themes. The solution is to define text colours at the token level for each theme, then run an automated contrast audit against every background token that text appears on. Tools like the axe DevTools browser extension and the WebAIM Contrast Checker can automate most of this process, but manual spot-checking of high-priority screens, onboarding, dashboards, settings, is still necessary because automated tools cannot always predict how colours interact in complex component layouts.

For SaaS companies serving regulated industries such as healthcare or finance, accessibility in dark mode is also a compliance consideration. Products that fail to meet WCAG standards in either theme may not satisfy the accessibility requirements of regulations such as the EU Web Accessibility Directive or Section 508 in the United States. Building a dark theme from a properly tokenised system makes compliance far easier to demonstrate, because the relationship between every text colour and its background is explicit and documented.

Dark mode for data visualisation and dashboards

This is the area where the largest number of SaaS products visibly struggle. Analytics dashboards, revenue trackers, project management boards and operational tools all depend on charts and data tables as core features. When dark mode is bolted onto a product whose charts were designed for a light background, the results are predictable: grid lines become invisible, axis labels blend into the background, data series overlap and lose distinction, and heat-map colours that communicated intensity on white become muddy or misleading on dark.

The correct approach is to design charts specifically for the dark theme rather than adapting light-mode charts after the fact. That means selecting a dark-compatible grid-line colour, defining data-series palettes with sufficient luminance separation, adjusting text annotation colours for readability, and reconsidering the use of area fills and opacity in stacked charts. Many charting libraries, including Chart.js, D3 and Recharts, now support theme-aware configuration, so teams do not need to rebuild their entire charting infrastructure to support this. They do need to invest time in specifying and testing the dark palette, which is work that almost always gets deprioritised under shipping pressure.

We see this pattern clearly when building custom learning management systems. For the KV School of Psychology, a Chennai-based psychology school, we built a custom e-learning platform with course dashboards and student progress tracking. Data-display clarity was central to the design. Applying the same principle to dark mode means ensuring that progress bars, completion indicators and quiz results remain legible and semantically clear regardless of which theme a student has selected. A dark mode that makes a progress bar look like a gaping hole in the interface defeats the purpose of the feature.

Component design and interactive state handling

Every interactive element in a SaaS product has multiple states: default, hover, focus, active, disabled, loading and error. In light mode, designers and developers are accustomed to expressing these states through a combination of border changes, background shifts, icon changes and subtle shadow adjustments. In dark mode, several of these techniques become less effective.

Shadows are the most obvious casualty. A light-mode card elevated above its neighbours by a soft drop shadow will appear flat in dark mode, because the shadow is no longer visible against a dark surface. The fix is to replace shadow-based elevation with a surface-layer system: each successive elevation level uses a slightly lighter background colour, creating a visible stacking context without relying on shadow at all. This approach, popularised by Material Design, has become the de facto standard for dark themes and is supported natively by most modern design systems.

Focus indicators present another challenge. Keyboard and screen-reader users rely on visible focus rings to navigate interfaces. A light-blue focus ring that is clearly visible on a white background may be entirely lost against a dark blue or purple surface. Design tokens for focus indicators must be defined with both themes in mind, and ideally use a colour that is guaranteed to contrast against every surface colour in the system, often a bright, saturated hue that stands out in both light and dark contexts. This is not just a usability concern. It is an accessibility requirement under WCAG 2.1 Success Criterion 2.4.7, which mandates that any keyboard-operable interface have a visible focus indicator.

When to use a professional dark mode design audit

Some SaaS teams attempt dark mode as a weekend project by a front-end developer who inverts a few CSS variables and ships the result. For internal tools used by a handful of people, this may be adequate. For customer-facing products, especially those in regulated sectors, those with complex data interfaces or those competing in markets where dark mode adoption rates are high, a professional audit is worth the investment.

A structured dark mode audit covers several areas that ad hoc development rarely touches. It begins with a contrast and token review across every screen, identifying colour combinations that fail WCAG standards. It moves through component-level testing to confirm that every interactive element behaves correctly across all states in the dark theme. It includes a data-visualisation review, checking that charts, tables and dashboards remain informative and accurate. It covers the full user journey from onboarding through to advanced features, because dark mode problems often hide in screens that receive less design attention, such as error states, empty states, account settings and help documentation.

For SaaS companies that have already shipped a dark mode and are seeing user complaints, or no complaints but rising support tickets about eye strain and usability, an external audit often reveals issues that internal teams have become desensitised to. We built a modern website for the practice of Dr Raj Palaniappan, a Chennai-based bariatric surgeon, with careful attention to how medical information is presented across different viewing conditions. Patient portals and health SaaS tools benefit from the same level of attention to theme consistency, because the information being displayed is often dense and requires careful reading under varied lighting conditions.

Beyond audits, the broader discipline of intentional interface design applies equally to light and dark themes. Our website development service incorporates theme architecture into the build process for every project, so that dark mode is not retrofitted after launch but designed in from the beginning. Similarly, our graphic design service produces brand identity systems with dark-theme variants built in, so brand colours, typography and illustration styles are specified for both contexts before any development begins.

The step-by-step process for fixing a broken dark mode

For teams that need to remediate an existing dark mode implementation, the following sequence minimises disruption and maximises the quality of the outcome.

Audit the current state

Before changing anything, document what exists. Run a contrast audit across every screen in the product. List every colour currently used in the dark theme, note its contrast ratio against every background it appears on, and flag every combination that fails WCAG AA. Also collect any user feedback about dark mode, from support tickets, app store reviews and user interviews, and categorise it by screen and feature. This baseline makes it possible to measure improvement objectively.

Define a dark-mode token set

Work from the audit results to build a complete set of design tokens for the dark theme. Start with backgrounds and surfaces, then text colours, then borders and dividers, then interactive states, then data-visualisation colours. Every token should be chosen with reference to the contrast ratios it must achieve. This step should involve both designers and developers, because the token set becomes a shared contract that both disciplines implement against.

Rebuild components against the new tokens

Update the component library so that every component, buttons, inputs, cards, dropdowns, tables, modals, toggles, references the dark-mode tokens rather than overriding colours individually. This is the most labour-intensive step but also the most impactful, because it ensures that the fix is systematic rather than piecemeal. A component rebuilt against the correct token set will automatically be correct wherever it appears in the product, including screens that were not part of the original audit.

Redesign charts and data displays

Charts and data-heavy components almost always require bespoke attention. Work through each chart type in the product and define a dark-compatible palette for its data series, grid, axes and annotations. Test each chart with real data at realistic densities, not just the clean example data used during development, because crowded charts are where dark mode problems most often appear. If the product uses a charting library, check whether it supports theme switching natively and configure it accordingly.

Test across devices and display types

Dark mode renders differently on OLED screens, LCD screens, phones, tablets, laptops and external monitors. A colour combination that looks acceptable on a calibrated desktop monitor may be uncomfortably bright on a phone screen viewed in a dark room, or too dim on an older LCD with reduced contrast. Test on physical devices in the lighting conditions your users are likely to be in, which for SaaS often means dim offices and late-night work sessions. User testing with real participants in dark mode will surface problems that no amount of internal review will catch.

Extend the theme to every customer touchpoint

A dark mode that covers the web application but not the help centre, onboarding emails or support documentation creates a jarring transition. Audit every public-facing surface and implement the dark theme consistently. If email templates are part of the product experience, such as notification digests or weekly summary reports, build dark-mode variants or use neutral colour schemes that work acceptably on both light and dark email clients.

Dark mode trends and emerging considerations

The dark mode landscape continues to evolve. Operating systems now detect ambient light levels and suggest theme changes automatically. Some interfaces are experimenting with adaptive themes that shift between light and dark based on the time of day or the user’s location. Others are exploring OLED-black themes that use true black (#000000) on devices where it genuinely saves battery life, paired with carefully calibrated text colours that prevent eye strain.

One emerging practice is the use of dynamic colour extraction, where an interface derives its dark-theme colours from the brand’s primary colour. This keeps the brand presence strong in dark mode while reducing the design work needed to specify an entire palette. The risk is that automatically derived colours may not always achieve the contrast ratios needed for accessibility, so teams that adopt this approach still need to validate the results against WCAG standards.

Another trend worth noting is the increasing use of dark mode in B2B SaaS products specifically. Tools used by developers, analysts, operations staff and creative professionals have led the adoption, and the expectation has spread into enterprise software across finance, healthcare and logistics. For SaaS companies targeting these markets, a well-executed dark theme is no longer a differentiating feature, it is table stakes. The differentiator is the quality of the implementation, which separates products that genuinely reduce eye strain and improve focus from those that simply offer the option.

The demand for polished, consistent interfaces across both themes also intersects with how a brand is perceived more broadly. For product-led SaaS companies where the interface is the primary brand touchpoint, the quality of the dark theme contributes directly to brand perception. We see this principle in action across our portfolio. The Waiipod project involved building a bold, modern visual identity for a media platform focused on conscious dialogue, where interface design and brand identity are inseparable. A SaaS product occupies the same territory: the interface is the brand, and every theme variant must carry that brand forward with equal intention.

Frequently asked questions

Does dark mode actually reduce eye strain?

Research on this topic is mixed, but the consensus among ophthalmology and human-computer-interaction communities is that dark mode can reduce eye strain in low-light environments, particularly for users who spend extended periods reading text on screens. The benefit is most pronounced when the ambient light level is low and the screen is the brightest light source in the room. In well-lit environments, the advantage is less clear, and some users find dark mode causes more fatigue because the pupil remains more dilated, increasing depth of field and making the text appear slightly less sharp. The practical conclusion is that offering both themes, and letting users choose, is the right approach, because individual preference and environmental context vary significantly.

What contrast ratio should I aim for in dark mode?

WCAG 2.1 requires a minimum contrast ratio of 4.5 to 1 for normal text and 3 to 1 for large text against their background. These apply equally to dark and light themes. In practice, teams should aim higher than the minimum where possible, because dark mode environments often compound contrast issues, a user working in a dim room with a dark interface is already operating at a disadvantage for visual acuity, and insufficient contrast makes that worse. A ratio of 7 to 1 or higher for primary text is a reasonable target, while secondary text can comfortably sit at the 4.5 to 1 minimum. Tools such as the WebAIM Contrast Checker and the Stark plugin for Figma can automate ratio calculations during design.

Should I use pure black for the dark mode background?

Most design systems and accessibility guidelines recommend against pure black (#000000) as a primary background. The problem is that the extreme contrast between pure black and white or near-white text can cause a visual phenomenon called halation, where the text appears to bleed or glow at the edges, especially on LCD and OLED screens. This is uncomfortable for users and can be particularly problematic for readers with astigmatism. A very dark grey, typically in the range of #121212 to #1E1E1E, provides the dark aesthetic without the harshness of pure black. Material Design, Apple’s Human Interface Guidelines and most enterprise design systems follow this recommendation.

How do I handle dark mode in email templates?

Email clients have limited and inconsistent support for dark mode. Some, including Apple Mail and the iOS Mail app, apply their own dark mode transformation to incoming messages, which can produce unpredictable results. Others ignore dark mode preferences entirely. The most reliable strategy is to design email templates with neutral, mid-tone backgrounds and sufficient contrast that works acceptably in both light and dark clients. Where possible, use CSS media queries that detect the user’s colour scheme preference and adjust accordingly, but always test across major email clients because support varies significantly. For SaaS products that send frequent notification or digest emails, investing in a neutral template design that degrades gracefully is more practical than maintaining separate light and dark email templates.

Does dark mode save battery on laptops and phones?

On devices with OLED or AMOLED screens, dark mode can meaningfully reduce power consumption because OLED pixels produce their own light and a black pixel is essentially off. Studies from Google and other sources have shown battery savings of up to 60 percent in certain usage scenarios on OLED devices when dark themes are used. On LCD screens, which use a backlight that is always on regardless of the image content, the savings are negligible or nonexistent. Given the diversity of device types in any user base, battery savings should not be the primary argument for implementing dark mode, user preference, accessibility and brand consistency are stronger reasons, but the battery benefit is a genuine advantage for a subset of users and can be mentioned as a secondary benefit in product communications.

How long does a proper dark mode implementation take?

The timeline varies significantly depending on the complexity of the product and the state of the existing design system. For a SaaS application with a well-structured component library and a complete set of design tokens, implementing a dark theme can take two to four weeks of focused design and development work. For products that lack a component library or whose current design is inconsistent, the timeline extends because the team must first establish the design foundation before building the theme on top of it. In either case, treating dark mode as a first-class design project, with dedicated design time, proper testing and user validation, produces a measurably better outcome than treating it as a CSS variable swap. For teams that need to assess where their current implementation stands, a focused dark mode design audit can provide a clear picture of the work required and help prioritise it against other roadmap items. Explore our web design and development resources for further guidance on interface design decisions that affect product quality.

If your SaaS product needs a dark mode that works as well as your light mode, or if you are building a new product and want both themes designed correctly from the start, our team at Monk Creatives can help. Reach out at info@monkcreatives.com or visit our contact page to start the conversation.

Leave a Reply

Your email address will not be published. Required fields are marked *

Let's Create Together

Tell us about your brand — our creative team gets back to you fast with fresh ideas and clear next steps.

  • Branding, design & content that stands out
  • A dedicated creative team for your brand
  • Transparent pricing — no hidden fees

Get a Free Consultation

Takes 30 seconds

Select a service…
  • Branding & Identity
  • Logo Design
  • Graphic Design
  • Web Design & Development
  • Social Media Management
  • Content Creation
  • Search Engine Optimization (SEO)
  • Digital Marketing
  • Video & Motion
  • Other