winxp.vercel.app

WinXP (winxp.vercel.app) is a browser-based recreation of the Windows XP desktop built with React and Hooks. It runs entirely client-side — no backend is involved — so the "operating system" you see is really a set of React components managing window state, a taskbar, a start menu, and individual apps like Minesweeper, Notepad, Internet Explorer, Winamp, Paint, and My Computer. This explains both why it feels like a desktop and why it depends on JavaScript to render anything at all.

The core idea: a desktop as component state

A real OS keeps track of which windows are open, where they sit, and which one has focus. WinXP does the same thing, but the "kernel" is React state.

• Functional components + Hooks — The project is described as "Windows XP in React and Hooks," meaning state and lifecycle logic live in function components rather than class components.
• Client-side only — There is no server rendering the desktop or storing your files. Everything happens in the browser tab.
• Composition over a real OS — Each visible element (window, taskbar button, start menu entry) is a component that reads from and updates shared state.

What the page evidence shows

The rendered output includes recognizable XP shell elements and apps:

This tells you the shell and the apps are separate pieces assembled into one screen, which matches the "each app is its own component" design.

How window management likely works

Window management is the part that makes it feel like an OS. In a React implementation, it usually breaks down into a few pieces of state:

1. A list of open windows — each entry holds an app identifier, position, size, and z-index (stacking order).
2. A focus/active window — clicking a window or taskbar button updates which window is on top.
3. Open/close/minimize actions — these mutate the window list, and the taskbar re-renders to match.

The input is a user action (clicking an icon, dragging a window). The action updates state. The expected result is that the desktop re-renders to reflect the new window arrangement — the same input → state → render loop React uses everywhere.

The taskbar and start menu

The taskbar is essentially a live view of the open-window list plus a clock. The start menu is a component that toggles visibility and lists launchable apps. Because both read the same state as the windows, opening an app from the start menu and clicking its taskbar button stay in sync automatically.

Why each app is a separate component

Treating Minesweeper, Notepad, Winamp, and the rest as independent components keeps the code modular:

• Isolation — A bug in the Minesweeper grid logic doesn't touch the window manager.
• Reuse — Every app plugs into the same window frame (title bar, menu bar, close button).
• Lazy rendering — An app only needs to render when its window is open.

For example, the Winamp component in the evidence shows a playlist with tracks and durations ("Diablo Swing Orchestra - Heroines (5:22)", "0:00 / 43:35"). That's self-contained UI state — playback position, track list — that doesn't need to know anything about the desktop around it.

Why it needs JavaScript (and shows a blank page without it)

The page's own notice — "You need to enable JavaScript to run this app" — is the key constraint. Because the entire desktop is rendered by React in the browser:

• If JavaScript is disabled or blocked, React never mounts, and you get a blank page.
• If a script fails to load (network, extension, or CSP issue), the same blank result occurs.
• There is no static HTML fallback of the desktop, since the shell itself is generated client-side.

So "blank page" is expected behavior when the client-side app can't start, not a sign the project is broken.

No backend required

Nothing here needs a server to function:

• No accounts or storage — Files you "create" in Notepad and drives shown in My Computer are simulated in the browser.
• No data leaves the tab — The apps are demonstrations, not real file or network tools.
• Deployment is static — Hosting on a platform like Vercel fits a purely client-side React build.

What this means for you

If you want to understand or rebuild something like this, the mental model is: one React app = a fake OS, where Hooks hold the window list and active state, the taskbar and start menu are views of that state, and each app is an isolated component mounted inside a shared window frame. The only hard requirement for it to run is a browser with JavaScript enabled.

WinXP is a browser-based recreation of the Windows XP desktop built with React and Hooks. If you see a blank page or can't interact with anything, the most common cause is that JavaScript is disabled or blocked. The site's own page states: "You need to enable JavaScript to run this app." Enable JavaScript for the site, then reload — that resolves the issue in most cases. If it still fails, the problem is usually a browser extension, strict privacy setting, or an outdated browser.

What WinXP actually is

WinXP (winxp.vercel.app) is a web app that simulates the Windows XP interface inside your browser. According to the site, it includes:

• Internet Explorer — a simulated browser window
• Minesweeper — the classic game
• My Computer — a file-explorer-style window
• Notepad — a text editor
• Winamp — a media-player-style window with a playlist
• Paint — a drawing app

Because everything runs client-side in React, the entire experience depends on JavaScript executing in your browser. There is no server-rendered fallback, so a blocked script means a blank screen.

Fixes to try, in order

1. Enable JavaScript

Check your browser's site settings for winxp.vercel.app and make sure JavaScript is allowed. In Chrome or Edge: Settings → Privacy and security → Site settings → JavaScript, then confirm the site isn't in the "Not allowed" list. Reload the page afterward.

2. Disable ad blockers or strict privacy extensions for this site

Extensions like ad blockers, script blockers (NoScript, uBlock Origin in hard mode), and privacy tools can block the React bundle. Temporarily allow the site in those extensions, or open the page in a private/incognito window with extensions disabled to test.

3. Try a different browser

Modern versions of Chrome, Firefox, Edge, and Safari should work. If one browser fails, test another to isolate whether the problem is browser-specific.

4. Refresh or hard-reload

A cached or partially loaded bundle can leave the page blank. Use a hard reload (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to force a fresh fetch.

5. Check for network or firewall interference

Corporate networks, VPNs, or firewalls that block Vercel-hosted assets can prevent the app from loading. Try a different network if possible.

Quick reference

What to expect once it works

When JavaScript runs correctly, you should see the Windows XP desktop with a taskbar and icons for Internet Explorer, Minesweeper, My Computer, Notepad, Winamp, and Paint. The clock in the taskbar (shown as "1:18 PM" in the site's own interface) and the Start-menu-style layout confirm the app has loaded properly. If you see the desktop but individual apps don't open, that's a separate issue — usually a single blocked resource rather than a full JavaScript failure.

The site does not mention any login, account, or payment requirement, so no sign-in step should be blocking you. If a blank page persists after enabling JavaScript and disabling extensions, the issue is most likely on the network or browser-version side rather than with the app itself.

WinXP (winxp.vercel.app) is a browser-based recreation of the Windows XP desktop built with React and Hooks. It runs entirely in your browser and includes interactive simulations of several classic XP programs: Minesweeper, Internet Explorer, Notepad, Paint, Winamp, and My Computer. You need JavaScript enabled for the app to load.

What's included

How each piece behaves

Minesweeper

The game window opens with its own Game and Help menus, matching the original layout. It's the main interactive game in the set.

Winamp

Winamp comes loaded with a sample playlist rather than an empty player. The visible tracks include:

1. Diablo Swing Orchestra – Heroines (5:22)
2. Eclectek – We Are Going To Eclecfunk Your Ass (3:10)
3. Auto-Pilot – Seventeen (3:34)
4. Muha – Microphone (3:01)

The player shows a total runtime of 43:35 with standard transport controls, so you can see how playback and track switching work.

Internet Explorer

The simulated browser includes the familiar File/Edit/View/Favorites/Tools menu bar, a Back/Search/Favorites toolbar, and an address bar. It loads a Google-style page with links for Gmail, Images, and Search, plus a Taiwan-region footer.

Notepad, Paint, and My Computer

These open as standard windows. My Computer shows system tasks (view system information, add or remove programs, change a setting), other places (My Network Places, My Documents, Shared Documents, Control Panel), and details about drives and stored files.

Things to know before you try it

• JavaScript is required. Without it, the page only shows a message asking you to enable JavaScript.
• Everything is a simulation. These are interactive recreations inside a single web app, not the real programs, and they don't connect to your actual file system or the live internet.
• No pricing or account details are indicated on the page, so there's nothing to sign up for based on the available information.

If you want a quick nostalgia trip or a lightweight way to show someone what the XP desktop looked like, opening the site and clicking through the taskbar icons is the fastest path. Start with Minesweeper if you want something to actually play, or Winamp if you want to see the media player in action.

WinXP at winxp.vercel.app is a fan-made, browser-based recreation of the Windows XP desktop, built with React and Hooks. It runs entirely in your browser and requires JavaScript to be enabled — if scripts are blocked, you'll just see a notice telling you to turn them on. It is not an official Microsoft product, so treat it as a nostalgic demo rather than a real operating system.

What you can actually do there

The site reproduces the XP look and drops you into a desktop with a taskbar, Start-style navigation, and a set of working mini-apps. Based on the page content, the available apps include:

The desktop also shows a clock (for example, "1:18 PM") and a system tray area, which is what sells the illusion of a full XP session.

How it behaves

Everything is client-side. There's no install, no sign-in shown on the page, and no download — you open the URL and the desktop loads. The apps are simulations: Internet Explorer renders a fake page rather than browsing the real web, and Winamp shows a playlist and progress bar rather than playing your files.

A few practical notes:

• JavaScript is mandatory. The page explicitly states you need to enable JavaScript to run the app.
• It's a demo, not a shell. You can't install software, access your real C: drive, or run Windows programs.
• Expect a single-page experience. All the windows live inside the browser tab.

Who it's for

This is aimed at people who want a quick nostalgia hit or want to see how far a React app can go in mimicking a desktop OS. If you're looking for a way to run legacy Windows software, this won't do it — you'd need a real emulator or virtual machine instead. If you just want to click around a convincing XP desktop and play Minesweeper in a tab, it's exactly the right thing.