98.js: the website that brings back a familiar desktop
10 Nov 2026 · By the Boring Websites editors
98.js recreates a Windows 98 desktop inside a browser, with small utilities, games and screensavers sharing the same pretend computer. It is worth visiting for the details between tasks: a calculator's memory buttons, a cloud-covered desktop, and a screensaver that has become something to open deliberately.
In brief
- 98.js is a desktop remake with several separately developed applications, rather than a complete Windows installation.
- Live Chromium checks confirmed Notepad text entry and a Calculator result of 5 for 2 + 3.
- Primary documentation explains additions such as Sound Recorder's larger waveform and Paint's branching undo history.
- Files and themes belong to the browser recreation; local storage is not a backup service.
Start with the desk, then open something small
The live 98.js desktop opened on 10 November 2026 with a cloudy background, two columns of icons at the left and a taskbar along the bottom. My Computer, Recycle Bin and My Documents shared the desktop with Paint, Solitaire and Calculator. A clock occupied the right-hand end of the bar. The scene looked ready for a very minor administrative task.
Double-clicking Notepad in that Chromium session opened an Untitled window with File, Edit, Search and Help menus. Entering a short sentence put it into the text area; opening Calculator added another program to the taskbar. These checks establish a working fragment of the desktop, rather than just a picture of one. The blank page and the arithmetic pad were available together, with no larger assignment attached.
The 98.js project README calls the site a web-based desktop remake. Its component list includes utilities, games, a Help Viewer and several credited outside projects. That description is more useful than assuming the page runs an original Windows installation. The subject is the desktop experience, assembled from browser applications. Familiar names identify the things being recreated, not a promise that every older program will run here.
A useful first visit can stay deliberately small: open a note, enter a few words, then open the calculator beside it. The result is a little working arrangement with very little work in it. The interest is in the surrounding furniture: a title bar makes a scrap of text into a document, while a taskbar gives that document a place among other open things.
There is no need to remember an earlier computer to follow that arrangement. The labels state their subjects plainly. The page offers objects to investigate rather than a single compulsory route through a story. An old hand may recognise a visual habit; a newcomer can inspect the same habit without borrowing someone else's nostalgia. The desktop supplies enough context for either reading.
Research for this guide combined the live desktop checks with the primary documentation linked below. Notepad entry, Calculator arithmetic and opening the Themes folder were exercised in Chromium; the more specialised application features are described as documented. Those limited checks do not establish compatibility across browsers or verify every game, menu and save operation. The rest of the visit can proceed without repeating that qualification at every icon.
Notepad and Calculator: useful differences at small scale
A note can stand on its own
The Notepad README links both the desktop and a standalone version. That is a practical distinction for a reader interested in the text editor alone: the application has an entrance separate from the surrounding recreation. Within the desktop, the short text-entry check produced a recognisable pairing of a document window and its taskbar entry. The document did not have to become anything more ambitious than a note.
The same Notepad documentation records work on clipboard-menu availability and focus, plus search and font selection. These are TODO entries, not a verified catalogue of present failures. They do reveal how much behaviour lives behind a simple editor. A menu must decide whether an action is available while the selection and keyboard focus move elsewhere. Reproducing a handful of labels is only the visible part of the job.
That makes Notepad a good first stop for understanding the project's scale. Its value here is not a claim that browsers need another place to type. It is the opportunity to examine a plain utility as a designed object. A mostly empty window gives its controls unusually little cover. The wording of a menu, the title of a document and the relationship to the desktop become the things worth noticing.
The arithmetic has a newer engine
According to the Calculator README, the recreation uses the Windows 10 Calculator engine, ported to the web by muzamil, with an interface recreated by Isaiah Odhner. The project therefore separates the age of the appearance from the origin of the arithmetic machinery. It is a particularly clear example of reconstruction through a newer component, rather than an attempt to preserve every underlying piece.
That README also records four departures from the Windows 98 application: mathematical symbols replace some textual labels, memory-clear and memory-recall buttons are disabled when nothing is stored, the decimal point appears only after entry, and scientific mode is unsupported. These details offer a better basis for comparison than a sweeping assertion of perfect accuracy. A small calculator can be faithful to an idea while making particular changes.
On the live 98.js desktop, clicking 2, addition, 3 and equals displayed 5. The MC and MR controls were disabled with empty memory in that session. This is a modest test, appropriately matched to a modest observation. The distinctive part is not that a web page can add two numbers; it is that the arithmetic sits inside a carefully specified piece of familiar desk equipment.
The decimal-point choice is worth pausing over because it communicates state with almost nothing. A mark that is always present and a mark that appears after an action make different suggestions about the number being entered. The memory controls do something similar through availability. Calculator gives a visitor small, concrete differences to inspect, without requiring an opinion about the superiority of an entire era of interface design.
Paint and Sound Recorder allow more than imitation
Paint keeps an alternative past
The bundled JS Paint README describes the painting application's extended editing features. One of the most interesting is nonlinear undo history: undoing and then taking a different action creates a branch rather than throwing away the abandoned sequence. The document identifies Edit, then History, as the route to that view. An ordinary correction becomes a choice between possible versions of the drawing.
That is a meaningful addition to a nostalgic interface. A brush stroke need not be final, but neither must it disappear when another route is tried. The idea fits the smallness of Paint particularly well: an unimportant sketch can become a place to experiment with different outcomes. The old-looking tool box is the invitation; a less restrictive history is one reason the remake can support a longer stay.
The Paint documentation also explains transparent images, arbitrary-angle rotation and a custom zoom scale. Its description of Image, then Attributes, gives a route to transparent mode; Image, then Flip/Rotate, handles rotation. These are documented options in the bundled project, rather than functions exercised for this article. They show that a familiar appearance can accommodate extra room for editing instead of fixing every feature at a historical boundary.
Its accessibility options are especially relevant to that distinction. The bundled README describes Eye Gaze Mode for coarse pointing devices and speech recognition for selecting tools, choosing colours and other actions. These additions should not be confused with a tested accessibility assessment of the entire 98.js desktop. They do make the painting project's purpose broader than visual imitation. The familiar canvas can be approached through a different kind of input.
Readers interested chiefly in that application can continue to the blog's JS Paint field guide. Within this article, its role is as one room in the larger desktop. Paint supplies a place to make an image, while the neighbouring utilities make the image feel like one possible use of a small computer. The shared setting changes the context without making the applications identical.
Sound Recorder gets a bigger view
The Sound Recorder README documents a simple extra feature: the window can be maximised to enlarge its slider and waveform display. The stated purposes are easier seeking through long audio and a clearer view of quiet audio. It is an unusually restrained enhancement. The program gets more space for the same subject, rather than a new set of ambitions.
Opening Sound Recorder on the live 98.js desktop produced a window with File, Edit, Effects and Help menus and a zero-length sound display. No recording or audio processing was tested. The documented enlargement is nevertheless a useful detail for a visitor to look for: the scale of the window is related to reading the sound, not merely to filling more of the screen.
The Sound Recorder documentation lists virtual-filesystem integration and several editing operations among its TODO items. That prevents a misleading leap from the presence of a shared desktop to the assumption that every application shares every facility. The remake gathers programs in one environment, but individual integrations have their own state. A common frame is not proof that the contents have become one uniform system.
Screensavers give doing nothing a program of its own
The Pipes README describes a Three.js recreation of the Windows 3D Pipes screensaver, available within 98.js as a program. It documents collision avoidance between pipes and a dissolve transition, and notes that its demonstration GIF is outdated. That last detail is useful source guidance: the current written description should not be silently replaced by whatever an older demonstration appears to show.
Pipes is an especially good fit for a field guide to uneventful websites. In this setting, a screensaver becomes something deliberately opened, rather than something waited for. Its pipes offer movement without requiring a task to be completed. The appeal is almost bureaucratically precise: a visitor has chosen a program whose job is to occupy the display. Leaving the computer alone acquires its own interface.
The same Pipes README mentions teapot and candy-cane surprises among its documented details. These are small variations inside a repeated visual premise, not a reason to turn the visit into a hunt with a checklist. A screensaver can remain pleasant without yielding every hidden object. The unusual thing is already in plain sight: a utilitarian desktop recreation has made room for an elaborate representation of inactivity.
A different geometry appears in the 3D FlowerBox README, which credits Kevin Shannon and describes a WebGL recreation of a Windows 95 screensaver. It also links a standalone version. That attribution usefully complicates the desktop's date label: the assembled environment contains a screensaver whose own documentation names another Windows version. The collection is held together by its setting, rather than by a claim that every component has the same origin.
Games bring a different sort of small occupation. The Minesweeper README credits Jon Ziebell and provides a standalone link, while the Solitaire README credits Radovan Janjic and links its original repository. Those separate credits matter. The desktop is a meeting place for recreated activities, and the work behind each activity remains identifiable rather than dissolving into a single anonymous retro aesthetic.
For a short visit, the screensaver makes a useful counterweight to the games and utilities. Notepad invites a sentence, Calculator a number, and a game a decision. Pipes can be approached simply as a display. That range gives the desktop its quiet variety. Several kinds of attention fit inside the same ordinary frame, including the sort that would rather watch something than finish something.
Themes and files make the desktop more than a backdrop
The main project README documents loading Windows themes and dropping files onto the desktop into a virtual filesystem. During the live 98.js check, double-clicking Themes opened an Explorer window for the desktop's Themes folder. The distinction is worth keeping: opening that folder was observed, while the broader theme-loading feature is documented. No claim of testing every included theme follows from opening a directory.
The Explorer README describes one application serving both Windows Explorer and Internet Explorer. That shared role makes the browser recreation agreeably nested: an actual browser contains a desktop whose own browsing window represents both folders and the web. It also explains why a folder can feel like a destination here. The navigation apparatus has become part of what the visitor came to see.
For the storage model, the filesystem setup source is more informative than the general feature list. It configures an OverlayFS with IndexedDB as the writable side and an XmlHttpRequest-backed readable side. In plain terms, the code combines a browser database for changes with an initial set of files retrieved from the website. That is a source-code observation, not a guarantee about how long a particular browser will retain saved material.
This arrangement helps explain the desktop's relationship to its contents. The recreation can start with supplied files while providing somewhere for changes to go. The browser remains the host of that arrangement. A file appearing in the pretend desktop should not be mistaken for a promise of independent storage elsewhere. Anything worth keeping deserves an ordinary exported copy, rather than an assumption based on a familiar-looking folder.
Themes serve a different purpose from files. They make the setting itself available for variation. A desktop that can change its appearance is a more personal kind of exhibit than a fixed screenshot, even if the underlying premise remains the same. The interesting question becomes which details feel essential to the place and which are merely its current clothes. Familiarity survives some changes more easily than others.
A collection with visible joins
The Winamp README identifies its player as Webamp by Jordan Eldredge and links the separate Webamp website. Alongside the Calculator engine credit, the game credits and the screensaver documentation, it makes the desktop's construction readable as a collection of projects. The shared environment brings them together without erasing their separate subjects. Each has something more specific to say than simply looking old.
The licence distinction is equally specific. The 98.js README describes the overall project as source-available and not yet licensed as open source. That should not be flattened into a claim that every visible repository is open source under one common licence. Credits explain who supplied a component; licence statements answer a different question. The article's interest in the site does not require blurring the two.
As a neighbour to the blog's Windows93 field guide, 98.js offers another reason to think about the desktop as a place to visit. The comparison is an invitation to examine two websites separately, rather than assume all retro desktops share one purpose. Here, the most rewarding route follows the ordinary utilities and the particular choices recorded around them.
That attention to small procedures also places the article comfortably beside The Bureau of Tiny Approvals in the Boring Websites network. The connection is editorial: a modest action can be enough of a subject for a website. In 98.js, even a correctly disabled memory button has something to contribute. A quiet computer has quite a lot of furniture.
FAQ
Does 98.js run an original Windows 98 installation?
The project README describes a web-based desktop remake. The Calculator and other component documents identify separately recreated applications and newer underlying technology. The site should be approached as a browser reconstruction, not as a verified installation of the original operating system.
Which small features were checked live?
On 98.js in Chromium on 10 November 2026, Notepad accepted a short sentence, Calculator returned 5 for 2 + 3, and the Themes folder opened in Explorer. The documentation supplies the other feature descriptions; this was not a complete compatibility test.
Can individual applications be opened separately?
The Notepad, Sound Recorder and 3D FlowerBox documentation each provide standalone links. Those offer a shorter route for readers interested in one component rather than the desktop setting.
Should the virtual desktop be used as a backup?
No backup guarantee was established. The filesystem setup source uses browser IndexedDB for its writable storage. A familiar desktop appearance does not establish independent safekeeping; important work should have a separately retained copy.