CSS update Media Feature

Beginner
⏱️ 6 min read
📚 Updated: Jul 2026
🎯 4 Examples
Media Queries

What You’ll Learn

The update media feature detects how quickly a display can change content after rendering. Adapt animations and transitions for fast monitors, slow e-readers, and static print output.

01

@media

Media query.

02

fast

Monitors.

03

slow

E-ink.

04

none

Static.

05

animate

On fast.

06

fallback

On slow.

Introduction

Not every screen updates at the same speed. Your laptop redraws content dozens of times per second. An e-reader’s e-ink display refreshes slowly and can ghost between frames. Printed paper cannot update at all once ink hits the page.

The CSS update media feature lets you detect that refresh capability and tailor animations, transitions, and hover effects accordingly.

Definition and Usage

Write @media (update: fast) before adding CSS animations on normal screens. Use @media (update: slow) to disable transitions on e-readers. Use @media (update: none) for static output where hover states never apply.

💡
Beginner Tip

The old reference confused update with the general @media rule. update is a specific media feature about display refresh speed — not “how to update CSS dynamically.”

📝 Syntax

Use (update: value) inside @media:

syntax.css
/* Fast-updating screens (monitors, phones) */
@media (update: fast) {
  /* Animations and transitions OK */
}

/* Slow-updating displays (e-readers) */
@media (update: slow) {
  /* Disable animations, simplify hovers */
}

/* Static output (printed paper) */
@media (update: none) {
  /* Show static fallbacks */
}

Accepted Values

fast Smooth updates. Monitors, laptops, phones. Animations are fine.
slow Layout can change but animations look choppy. E-ink e-readers.
none Cannot update after render. Printed paper, some static displays.

update vs @media rule

@media (update: fast) A specific media feature — tests display refresh speed.
@media screen and (min-width: 48rem) The general @media rule — can combine types and features.

update vs prefers-reduced-motion

@media (update: slow) Hardware refresh speed — e-ink cannot animate smoothly.
@media (prefers-reduced-motion: reduce) User preference — respect motion sensitivity on any device.

Basic Example

update-basic.css
@keyframes bounce {
  50% { transform: translateY(-8px); }
}

@media (update: fast) {
  .badge {
    animation: bounce 1s ease-in-out infinite;
  }
}

Default Value

There is no CSS default. The matched value depends on the output device. Most desktops and phones report fast.

Syntax Rules

  • Use parentheses: (update: fast) — not @media update alone.
  • Boolean form: (update) matches fast or slow; not (update) matches none.
  • Combine with OR: (update: slow), (hover: none) for e-readers or touch devices.
  • Do not call update a CSS property — it is a media feature.
  • Also respect prefers-reduced-motion alongside update queries.

Related Topics

  • print — printed output media type
  • hover — hover capability detection
  • scan — progressive vs interlaced scanning
@media (update: fast) @media (update: slow) @media (update: none)

⚡ Quick Reference

QuestionAnswer
Feature nameupdate
What it measuresHow quickly the display can change rendered content
Valuesfast, slow, none
Most common todayfast (monitors and phones)
Animate onupdate: fast
Simplify onupdate: slow or update: none
Browser supportBaseline — all modern browsers (since 2023)

When to Use update

Reach for update when display refresh speed affects the user experience:

  • CSS animations — Enable only on update: fast screens.
  • E-readers — Disable transitions and hover effects on update: slow.
  • Static output — Show link underlines and full details on update: none.
  • Battery saving — Avoid unnecessary repaints on slow-updating devices.
  • Progressive enhancement — Layer animations on top of static fallbacks.

👀 Live Preview

On fast-updating screens, the badge below bounces. On slow devices it stays amber without animation:

Update Speed Demo Your display’s refresh rate controls the effect Fast: bounces · Slow: static amber

Examples Gallery

Practice update with fast animations, slow transitions, static links, and combined queries.

📜 Core Patterns

Target display refresh speed with the update media feature.

Example 1 — Animation on fast-updating screens

Add a bounce animation only when the display updates quickly:

update-fast.css
@keyframes bounce {
  50% { transform: translateY(-8px); }
}

@media (update: fast) {
  .badge {
    animation: bounce 1s ease-in-out infinite;
  }
}
Try It Yourself

How It Works

Based on the MDN reference pattern. Animations only run where the display can refresh smoothly.

Example 2 — Disable transitions on slow displays

Remove hover transitions on e-readers and other slow-updating devices:

update-slow.css
.card {
  transition: background 0.3s ease;
}

@media (update: slow) {
  .card {
    transition: none;
    background: #fef3c7;
  }
}
Try It Yourself

How It Works

E-ink displays refresh slowly. Transitions cause ghosting and waste battery — static styles are better.

Example 3 — Static link underlines on none

Always show underlines when the output cannot update (no hover possible):

update-none.css
a {
  text-decoration: none;
}

a:hover {
  text-decoration: underline;
}

@media (update: none) {
  a {
    text-decoration: underline;
  }
}
Try It Yourself

How It Works

On static output, hover never fires. Show underlines by default so links are identifiable.

Example 4 — Combined with hover: none

Reveal hidden details on slow screens or when hover is unavailable:

update-combined.css
.details {
  display: none;
}

@media (update: slow), (hover: none) {
  .details {
    display: block;
  }
}
Try It Yourself

How It Works

Recommended CSS WG pattern: show compact info on e-readers and touchscreens where hover-reveal UX fails.

🛠 Usage Tips

  • Animate on fast — Wrap animations in @media (update: fast).
  • Simplify on slow — Remove transitions and hover-dependent layouts.
  • Static on none — Show all info upfront; no hover-only reveals.
  • Pair with reduced-motion — Also check prefers-reduced-motion.
  • Progressive enhancement — Base styles work everywhere; fast adds polish.

⚠️ Common Pitfalls

  • Confusing with @media ruleupdate is a feature, not the whole media query system.
  • Calling it a propertyupdate is a media feature inside @media.
  • Animations everywhere — Do not animate on slow e-ink without a fallback.
  • Hover-only content — On update: none or slow, hover may never work.
  • Ignoring user prefsupdate: fast does not override prefers-reduced-motion.

♿ Accessibility

  • No hover-only info — Reveal details on slow and touch devices automatically.
  • Respect reduced motion — Combine update: fast with prefers-reduced-motion: no-preference.
  • Readable static output — On update: none, ensure links and labels are always visible.
  • E-reader comfort — Avoid flashing animations on update: slow displays.
  • Progressive disclosure — Do not hide essential content behind fast-only animations.

🧠 How update Works

1

Browser checks refresh speed

Reports whether the display updates fast, slow, or not at all.

Detect
2

update value is matched

Compares fast, slow, or none in your query.

Match
3

@media rules apply

Animations, transitions, and layout adjust to the device speed.

Apply
=

Smooth on every device

Fast screens get polish; slow screens get clarity.

🖥 Browser Compatibility

The update media feature reached Baseline status in 2023 and is supported in all modern browsers.

Baseline · Widely available

Update media queries

Works in Chrome, Firefox, Safari, Edge, and Opera since 2023.

95% Global support
update media feature 95% supported

Bottom line: update is production-ready. Most users match fast; keep slow/none fallbacks for e-readers and print.

🎉 Conclusion

The update media feature detects display refresh speed — fast for monitors and phones, slow for e-readers, and none for static output. Use it to add animations only where they render smoothly.

Unlike the old reference, update is not the general @media rule. It is one specific feature that makes responsive design friendlier to every kind of screen.

💡 Best Practices

✅ Do

  • Animate on update: fast
  • Simplify on update: slow
  • Static fallbacks on none
  • Combine with hover: none
  • Respect reduced-motion

❌ Don’t

  • Confuse with @media rule
  • Call it a property
  • Animate on e-ink
  • Hide info on hover only
  • Skip static fallbacks

Key Takeaways

Knowledge Unlocked

Five things to remember about update

Use these points when adapting to display refresh speed.

5
Core concepts
📖 02

slow

E-readers.

Value
📄 03

none

Static.

Value
04

Not @media

A feature.

Syntax
05

Baseline

2023+.

Support

❓ Frequently Asked Questions

What does the CSS update media feature do?

The update media feature detects how quickly an output device can change content after it is rendered. Use update: fast for normal screens, update: slow for e-readers and low-power devices, and update: none for static output like printed paper.

What values does update accept?

Three keyword values: fast (smooth animations OK — monitors and phones), slow (layout can change but animations look choppy — e-ink readers), and none (output cannot update after rendering — printed documents).

How is update different from the @media rule?

The @media rule is the general syntax for all media queries. update is one specific media feature inside that rule — like min-width or orientation. Write @media (update: fast) { }, not @media update { }.

When should I use update in CSS?

Use update: fast before adding CSS animations. Use update: slow to disable transitions and hover effects on e-readers. Use update: none to show static fallbacks (like always-visible link underlines) for non-updating output.

Is the update media feature widely supported?

Yes in modern browsers. It reached Baseline status in 2023 and is supported in Chrome, Firefox, Safari, Edge, and Opera. Most desktops and phones report fast; test slow/none fallbacks for e-readers and print.

Practice in the Live Editor

Open the HTML editor and experiment with @media (update: fast) animations.

HTML Editor →

About the author

Mari Selvan M P
Mari Selvan M P 🔗

Developer, cloud engineer, and technical writer

  • Experience 12 years building web and cloud systems
  • Focus Full Stack Development, AWS, and Developer Education

I write practical tutorials so students and working developers can learn by doing—from databases and APIs to deployment on AWS.

5 people found this page helpful