How to Run a Starfield Screensaver on Your Second Monitor

How to Run a Starfield Screensaver on Your Second Monitor

Published on August 13, 2026

How to Run a Starfield Screensaver on Your Second Monitor

If you've got a second monitor that sits idle for stretches of the workday — dark, or worse, showing whatever was on screen last — there's an easy fix that doubles as a bit of nostalgia. WebLight's Starfield effect recreates the classic flying-through-space screensaver live in your browser: no download, no OS-level screensaver settings to dig through, just a tab you open and leave running on the screen you're not actively using.

What you'll need

  • A second monitor, tablet, or any spare screen you can point a browser at
  • A browser with WebGL and graphics acceleration turned on (most modern browsers have this on by default)
  • A dim or dark room, or at least a dark desktop background, since the field renders on black and reads best without bright light competing next to it

Step 1: Open Starfield on your spare screen

Open the Starfield effect in a browser tab and drag that window to your second monitor. Unlike your OS's built-in screensaver, this runs as long as the tab is open and visible — it won't wait for a timeout, and it won't interrupt anything on your primary display.

Step 2: Set Star Count first

Star Count (100–2000, default 1000) decides how dense the field looks before anything else matters, so dial it in before touching the other sliders. A lower count gives a sparser, calmer field that's easier to keep in peripheral vision during focused work; a higher count fills the screen with a busier, more immersive sky. Star Count is also the main performance cost of the effect, so if you're on integrated graphics or an older laptop, start low.

Step 3: Set Speed for how fast you want to feel like you're moving

Speed (1–200, default 50) controls how fast stars travel toward you. For a calm background you can work alongside, keep it low — 15–25 is a slow drift that doesn't pull focus. Push it up toward 100–150 if you want the classic hyperspace-jump feel instead.

Step 4: Adjust Star Size, Trail Length, and Warp Factor to taste

Star Size (10–200, default 50) sets how big each point renders — larger reads as closer or brighter, smaller reads as distant and fine. Trail Length (0–100, default 80) controls opacity: low values fade stars toward transparent for a wispy field, values near 100 keep every star sharp and solid. Warp Factor (0–100, default 50) adds a burst of extra acceleration as stars close in on the camera during the final stretch before they pass you — set it to 0 if you'd rather have a perfectly steady speed with just the natural perspective effect (the same reason things look faster as they pass close by, like a car near the road versus one far off).

Step 5: Pick a star color if you don't want white

The color swatch defaults to white but tints every star in the field to whatever color you choose. There's no separate color-temperature control on this effect — the swatch is the only color adjustment.

Step 6: Set Brightness and go fullscreen

Brightness (10–100, default 80) is the overall opacity of the field, layered on top of Trail Length — lower it to fade the whole sky toward transparent, or keep it high to let Trail Length do the work of solidity. Once everything's dialed in, select Go Fullscreen so the field fills the entire screen. Press Escape or move your mouse to bring back Exit Fullscreen whenever you need to step away.

Pro tips

  • If the animation stutters, lower Star Count before anything else. It's repositioning every point on screen every frame, so it's the single biggest lever for performance on slower hardware.
  • Stack Trail Length and Brightness carefully. They both push star opacity toward transparent and they compound — if stars look faint or nearly invisible, check that neither one is set too low, and make sure your color swatch isn't accidentally close to black against the black background.
  • A subtle setup works well for a second monitor you glance at, not stare into. Speed 10–20, Star Count 300–500, Star Size 20–30, Trail Length 40–50 gives you something alive in your peripheral vision without asking for attention.
  • The first load can take a moment. The Starfield renderer loads on demand rather than up front, so expect a brief delay the first time you open it or switch to it in a session — it only happens once per visit.

FAQ

Is this an accurate recreation of the classic Windows starfield screensaver? Yes — it reproduces the flying-through-space look of points streaming past and accelerating as they near the camera, rendered live in WebGL rather than played back as a video.

Will this actually replace my OS's screensaver? Not automatically — it runs as long as the browser tab stays open and visible, but it won't trigger on its own the way an OS-level screensaver does after idle time. Treat it as an always-on background for a screen you're deliberately leaving lit.

Will my slider settings be remembered next time? No. Every custom control on this effect resets to its default when you reload the page. There's no account or sync, so bookmark the effect or note down values you like.

Does this help prevent burn-in on an OLED monitor? Modern LCDs aren't very prone to burn-in in the first place, but a constantly moving field of stars is a reasonable choice for an idle OLED display compared to a static image, since nothing stays in the same pixels for long.

Do I need a powerful computer to run this smoothly? You need a browser with graphics acceleration turned on, but there's no strict hardware minimum — Star Count is the main cost, so a lower-end machine will handle it better with fewer stars.

Keep exploring

Try the Starfield effect on your spare screen, or browse the full screensaver classics library for more retro-inspired backgrounds. If you liked the space-travel feel, read our guide to the 3D Pipes screensaver — the other classic screensaver WebLight rebuilt the same way, with colorful tubes growing through 3D space instead of stars streaming past.