themx
← Back to themes

Scandinavian Clean

minimalist Visual style

Functional beauty in simplicity

Reference year: 2024

Compare this theme

Best for

Ecommerce, Editorial, SaaS

Less suitable for

  • Campaigns that need dense decoration and strong visual spectacle.

Live component preview

Try the sample controls. daisyUI uses compiled library classes; shadcn/ui uses React components from the New York registry. The three example layouts demonstrate styling with the selected tokens. All content is demo data.

Scandinavian Clean preview

Examples

Scandinavian Clean — Hero Section
Hero Section
Scandinavian Clean — Card Grid
Card Grid
Scandinavian Clean — Form
Form
Scandinavian Clean — Dashboard Layout
Dashboard Layout

Color Palette

Primary #2563EB
Secondary #64748B
Accent #F97316
Background #FFFFFF
Text #0F172A

Typography

Heading: Inter
Body: Inter

Key Characteristics

  • Clean lines and minimal ornamentation
  • Light airy color schemes
  • Functional typography
  • Subtle shadows and borders
  • Generous padding and margins
  • Content-first approach with clear hierarchy

Tags

hygge light functional simple

Scandinavian Clean design translates the Nordic design philosophy of “beautiful things that work” into digital interfaces. Like a well-designed piece of Swedish furniture, every element serves a purpose, nothing is superfluous, and the result is an interface that feels both effortless and considered. Light, airy, and supremely functional, this style prioritizes usability without sacrificing visual appeal.

When to Use

Scandinavian Clean is a versatile style that works across a wide range of applications — SaaS products, e-commerce platforms, content management systems, documentation sites, and corporate websites. It is particularly effective for products that serve daily use, where visual noise would become fatiguing over time. The style scales well from simple landing pages to complex multi-feature applications, making it a safe and effective choice for most web projects.

Key Visual Elements

The palette is dominated by white and light grays, with a single primary color (typically blue) used for interactive elements and calls to action. Borders are subtle (1px, light gray) or replaced entirely by whitespace and background color changes. Shadows, when used, are soft and minimal — just enough to suggest elevation without creating visual weight. Padding and margins are generous, following a consistent spacing scale (8px base unit). Every pixel of space is intentional.

Typography

Inter is the quintessential Scandinavian digital typeface — clean, highly legible, and perfectly suited to UI text at all sizes. Use a restrained set of sizes (perhaps 14px body, 18px subheading, 24px heading, 36px hero) with consistent line heights. Font weight variations (regular for body, medium for labels, semi-bold for headings) create hierarchy without introducing additional visual complexity.

Export style

Choose a library mapping or use the CSS variables in your own components. JSON includes the same mapping. Load the listed fonts separately.

:root {
  --tx-surface-bg: #FFFFFF;
  --tx-font-heading: "Inter", sans-serif;
  --tx-font-body: "Inter", sans-serif;
  --tx-surface-bg-image: none;
  --tx-card-bg: #FFFFFF;
  --tx-card-border: #E2E8F0;
  --tx-card-border-width: 1px;
  --tx-card-radius: 0.75rem;
  --tx-card-shadow: 0 1px 3px rgba(0,0,0,0.06);
  --tx-card-backdrop-blur: 0px;
  --tx-card-border-hover: #CBD5E1;
  --tx-card-shadow-hover: 0 4px 12px rgba(0,0,0,0.08);
  --tx-font-heading-weight: 600;
  --tx-font-body-weight: 400;
  --tx-text-muted: rgba(15,23,42,0.6);
  --tx-text-subtle: rgba(15,23,42,0.4);
  --tx-link-color: #2563EB;
  --tx-button-radius: 0.5rem;
  --tx-input-bg: #FFFFFF;
  --tx-input-border: #E2E8F0;
  --tx-text: #0F172A;
  --tx-primary: #2563EB;
  --tx-secondary: #64748B;
  --tx-accent: #F97316;
  --tx-media-filter: none;
}

Prompt Builder

Choose your project, UI library, and output. Prompts, documents, and exports use the same resolved theme values.

Example projects:

Use your own components with the exported CSS variables.

Components

Changing the page purpose selects suggested components. You can adjust them below.

Optional design layers

Apply a layout, then a surface effect, then a color mode. Fonts stay with the base theme. The output contains one final token set.

Scandinavian Clean

Live component preview

Try the sample controls. daisyUI uses compiled library classes; shadcn/ui uses React components from the New York registry. The three example layouts demonstrate styling with the selected tokens. All content is demo data.

Optional skills

Include skill references and installation instructions for your coding agent. Selecting a skill here does not install it.

Choose daisyUI or shadcn/ui to include its official skill.

Copy this prompt into your coding assistant. The task mode applies to the UI prompt.

Generated prompt

You are building a web application using Next.js with Tailwind.
Read existing project instructions and reuse installed components where available.

## Project
Project brief: Not specified
Target users: Not specified
Page purpose: Ecommerce
Framework: Next.js
CSS approach: Tailwind
UI library: Custom / no library
Tone: Professional

## Visual direction
Base theme: Scandinavian Clean (visual-style)
- Clean lines and minimal ornamentation
- Light airy color schemes
- Functional typography
- Subtle shadows and borders
- Generous padding and margins
- Content-first approach with clear hierarchy

## Resolved style
Use this final token set. It already includes the selected layers. These values take precedence over conflicting base characteristics.
Color palette: primary #2563EB, secondary #64748B, accent #F97316, background #FFFFFF, text #0F172A
Typography: Inter for headings, Inter for body text
Load the declared fonts with the required weights. Use system fallbacks when a font is unavailable.
```css
:root {
  --tx-surface-bg: #FFFFFF;
  --tx-font-heading: "Inter", sans-serif;
  --tx-font-body: "Inter", sans-serif;
  --tx-surface-bg-image: none;
  --tx-card-bg: #FFFFFF;
  --tx-card-border: #E2E8F0;
  --tx-card-border-width: 1px;
  --tx-card-radius: 0.75rem;
  --tx-card-shadow: 0 1px 3px rgba(0,0,0,0.06);
  --tx-card-backdrop-blur: 0px;
  --tx-card-border-hover: #CBD5E1;
  --tx-card-shadow-hover: 0 4px 12px rgba(0,0,0,0.08);
  --tx-font-heading-weight: 600;
  --tx-font-body-weight: 400;
  --tx-text-muted: rgba(15,23,42,0.6);
  --tx-text-subtle: rgba(15,23,42,0.4);
  --tx-link-color: #2563EB;
  --tx-button-radius: 0.5rem;
  --tx-input-bg: #FFFFFF;
  --tx-input-border: #E2E8F0;
  --tx-text: #0F172A;
  --tx-primary: #2563EB;
  --tx-secondary: #64748B;
  --tx-accent: #F97316;
  --tx-media-filter: none;
}
```
Use the CSS variables in your own components. Apply the heading and body font variables to their respective elements.

## Layout
- Use a consistent grid, generous whitespace, and functional content groups.

## Interaction
- Use subtle hover feedback and visible keyboard focus with minimal motion.

## Suitability notes
Use these limitations to assess the chosen page purpose. Explain any mismatch before applying an unsuitable treatment.
- Scandinavian Clean: Campaigns that need dense decoration and strong visual spectacle.

## Components
Generate the following components in this style:
- Navbar
- Cards
- Buttons
- Forms

## Quality requirements
Choose section order and visual emphasis from the real content and page purpose. Add only sections needed for the task.
Use supplied content. Label sample data. Do not invent testimonials, customer logos, statistics, or compliance claims.
Every interactive control must perform its declared action or be clearly labeled as a demo.
Include loading, empty, error, success, disabled, and focus states where applicable.
Use semantic HTML, visible keyboard focus, readable text contrast, and labeled form fields.
Ensure responsive design (mobile-first). Preserve reading order and avoid horizontal page overflow.
Respect prefers-reduced-motion. Keep essential content visible when animations are disabled.

## Verification
Check representative desktop and mobile widths, keyboard interaction, and relevant component states. Run available project checks and report what was actually verified.
Use Tailwind utility classes with the declared tokens.
Product context is incomplete. Label assumptions and treat the result as a draft until the missing context is supplied.