HomeBlog Posts
Fixing Theme Flash (FOUC) in Next.js with Material-UI CSS Variables

Fixing Theme Flash (FOUC) in Next.js with Material-UI CSS Variables

2025-07-21 by Remi Kristelijn

Fixing Theme Flash (FOUC) in Next.js with Material-UI CSS Variables

The Problem: Flash of Unstyled Content

When refreshing the page or navigating between routes, users experienced a brief flash of white background before the theme switched to their preferred dark mode. This is a common issue known as Flash of Unstyled Content (FOUC).

Why FOUC Happens

The flash occurs because:

  1. Server-Side Rendering: During SSR, the server doesn't know the user's theme preference
  2. localStorage Access: Theme preferences are stored in localStorage, which isn't available during SSR
  3. Hydration Mismatch: The server renders with a default theme, then the client switches to the user's preference
  4. Timing Issue: There's a brief moment between initial render and theme detection

The Solution: MUI CSS Theme Variables

The most effective solution is using MUI's CSS theme variables approach, which prevents SSR flickering by using CSS variables instead of JavaScript-based theme switching.

1. Theme Configuration with CSS Variables

Update src/lib/theme.ts to use MUI's CSS variables:

1import { createTheme } from '@mui/material/styles';
2
3const theme = createTheme({
4  cssVariables: {
5    colorSchemeSelector: 'class', // Use class-based theme switching
6  },
7  colorSchemes: {
8    light: {
9      palette: {
10        primary: {
11          main: '#1976d2',
12          light: '#42a5f5',
13          dark: '#1565c0',
14          contrastText: '#ffffff',
15        },
16        secondary: {
17          main: '#dc004e',
18          light: '#ff5983',
19          dark: '#9a0036',
20          contrastText: '#ffffff',
21        },
22        background: {
23          default: '#fafafa',
24          paper: '#ffffff',
25        },
26        text: {
27          primary: 'rgba(0, 0, 0, 0.87)',
28          secondary: 'rgba(0, 0, 0, 0.6)',
29        },
30      },
31    },
32    dark: {
33      palette: {
34        primary: {
35          main: '#90caf9',
36          light: '#e3f2fd',
37          dark: '#42a5f5',
38          contrastText: '#000000',
39        },
40        secondary: {
41          main: '#f48fb1',
42          light: '#f8bbd9',
43          dark: '#ec407a',
44          contrastText: '#000000',
45        },
46        background: {
47          default: '#121212',
48          paper: '#1e1e1e',
49        },
50        text: {
51          primary: '#ffffff',
52          secondary: 'rgba(255, 255, 255, 0.7)',
53        },
54      },
55    },
56  },
57  // ... typography and other theme options
58});
59
60export default theme;

2. ThemeRegistry with CSS Variables Provider

Update src/components/ThemeRegistry.tsx to use Experimental_CssVarsProvider:

1'use client';
2
3import { AppRouterCacheProvider } from '@mui/material-nextjs/v15-appRouter';
4import { Experimental_CssVarsProvider as CssVarsProvider } from '@mui/material/styles';
5import CssBaseline from '@mui/material/CssBaseline';
6import { useColorScheme } from '@mui/material/styles';
7import { createContext, useContext, useEffect, ReactNode } from 'react';
8import theme from '../lib/theme';
9
10// Theme context for managing theme state
11const ThemeContext = createContext<{
12  mode: 'light' | 'dark';
13  toggleTheme: () => void;
14}>({
15  mode: 'light',
16  toggleTheme: () => {},
17});
18
19export const useTheme = () => useContext(ThemeContext);
20
21// Theme provider component that manages theme state
22function ThemeProviderWrapper({ children }: { children: ReactNode }) {
23  const { mode, setMode } = useColorScheme();
24
25  useEffect(() => {
26    // Load theme preference from localStorage
27    const savedMode = localStorage.getItem('theme-mode') as 'light' | 'dark';
28    if (savedMode && (savedMode === 'light' || savedMode === 'dark')) {
29      setMode(savedMode);
30    } else {
31      // Check system preference
32      const prefersDark = window.matchMedia('(prefers-color-scheme: dark)').matches;
33      setMode(prefersDark ? 'dark' : 'light');
34    }
35  }, [setMode]);
36
37  const toggleTheme = () => {
38    const newMode = mode === 'light' ? 'dark' : 'light';
39    setMode(newMode);
40    localStorage.setItem('theme-mode', newMode);
41  };
42
43  return (
44    <ThemeContext.Provider value={{ mode: (mode === 'system' ? 'light' : mode) || 'light', toggleTheme }}>
45      {children}
46    </ThemeContext.Provider>
47  );
48}
49
50export default function ThemeRegistry({ children }: { children: React.ReactNode }) {
51  return (
52    <AppRouterCacheProvider>
53      <CssVarsProvider theme={theme} defaultColorScheme="light">
54        <ThemeProviderWrapper>
55          <CssBaseline />
56          {children}
57        </ThemeProviderWrapper>
58      </CssVarsProvider>
59    </AppRouterCacheProvider>
60  );
61}

3. Early Theme Detection Script

Add a script in src/app/layout.tsx to detect and apply the theme before any content renders:

1// src/app/layout.tsx
2<html lang="en" suppressHydrationWarning>
3  <head>
4    <meta name="emotion-insertion-point" content="" />
5    <script
6      dangerouslySetInnerHTML={{
7        __html: `
8          (function() {
9            try {
10              var mode = localStorage.getItem('theme-mode');
11              if (!mode) {
12                var prefersDark = window.matchMedia('(prefers-color-scheme: dark)').matches;
13                mode = prefersDark ? 'dark' : 'light';
14              }
15              document.documentElement.classList.add('mui-' + mode);
16            } catch (e) {
17              document.documentElement.classList.add('mui-light');
18            }
19          })();
20        `,
21      }}
22    />
23  </head>
24  <body>
25    {/* ... rest of layout */}
26  </body>
27</html>

Important: The suppressHydrationWarning attribute prevents hydration errors when the script adds theme classes to the <html> element.

4. Global CSS with CSS Variables

Create src/app/globals.css with CSS variables support:

1/* Global styles for MUI CSS theme variables */
2
3/* Initial theme setup - prevents flash of unstyled content */
4html.mui-light {
5  color-scheme: light;
6}
7
8html.mui-dark {
9  color-scheme: dark;
10}
11
12/* Set initial background colors to prevent flash */
13body {
14  background-color: #fafafa; /* Light theme default */
15  transition: background-color 0.2s ease;
16}
17
18html.mui-dark body {
19  background-color: #121212; /* Dark theme default */
20}
21
22/* MUI CSS Variables fallbacks */
23:root {
24  --mui-palette-primary-main: #1976d2;
25  --mui-palette-background-default: #fafafa;
26  --mui-palette-background-paper: #ffffff;
27  --mui-palette-text-primary: rgba(0, 0, 0, 0.87);
28  /* ... other light theme variables */
29}
30
31html.mui-dark {
32  --mui-palette-primary-main: #90caf9;
33  --mui-palette-background-default: #121212;
34  --mui-palette-background-paper: #1e1e1e;
35  --mui-palette-text-primary: #ffffff;
36  /* ... other dark theme variables */
37}

How This Solution Works

1. CSS Variables Approach

  • MUI automatically generates CSS variables for all theme colors
  • Components use these variables instead of JavaScript theme detection
  • No more theme.palette.mode === 'dark' conditions needed

2. Early Theme Detection

  • Script runs immediately in the <head> before any content renders
  • Detects user's theme preference from localStorage or system preference
  • Adds appropriate class (mui-light or mui-dark) to <html> element

3. Automatic Theme Application

  • CSS variables are automatically applied based on the class
  • All MUI components immediately use the correct theme
  • No JavaScript delay or theme switching logic needed

4. Hydration Safety

  • suppressHydrationWarning prevents errors when theme classes are added
  • Server and client render consistently
  • No hydration mismatches

Key Benefits

Before (Manual Theme Checking)

1// ❌ Old approach with manual theme checking
2<Box sx={{
3  backgroundColor: theme.palette.mode === 'dark' ? '#1e1e1e' : '#ffffff',
4  color: theme.palette.mode === 'dark' ? '#ffffff' : '#000000'
5}}>

After (CSS Variables)

1// ✅ New approach with CSS variables
2<Box sx={{
3  backgroundColor: 'background.paper',
4  color: 'text.primary'
5}}>

Testing the Implementation

Before the Fix

  • 🔴 White flash on page refresh
  • 🔴 Theme switching delay
  • 🔴 Manual theme condition checks
  • 🔴 Inconsistent SSR/CSR rendering

After the Fix

  • ✅ No flash on page refresh
  • ✅ Immediate theme application
  • ✅ Automatic CSS variable usage
  • ✅ Consistent server and client rendering

Best Practices

  1. Use Theme Tokens: Always use MUI theme tokens like background.paper, text.primary
  2. Avoid Manual Checks: Don't use theme.palette.mode === 'dark' conditions
  3. CSS Variables: Let MUI handle theme switching with CSS variables
  4. Class-Based: Use class-based theme switching for better performance
  5. Hydration Safety: Add suppressHydrationWarning to prevent hydration errors

Resources

Conclusion

By implementing MUI's CSS theme variables approach, we've completely eliminated the FOUC issue while simplifying the codebase. The solution provides:

  • Zero flickering on page refresh and navigation
  • Better performance with native CSS variables
  • Simplified code without manual theme checks
  • Consistent rendering between server and client

The key insight is that CSS variables provide immediate theme application without requiring JavaScript execution, making them the ideal solution for preventing SSR flickering in Next.js applications with Material-UI.