Today's Rock: the website that shows one rock a day

Today's Rock is a website that shows exactly one thing: a single procedurally generated stone, rotating in the middle of an otherwise empty page, labelled like a museum specimen. The same rock appears for every visitor on Earth for one calendar day, then disappears at midnight and is never kept. It is worth a look because it takes the most forgettable object imaginable and turns scarcity into the whole point.

In brief

• One rock per day, generated in the browser from the date, with no server and no stored assets.
• Everyone who visits during the same UTC day sees the identical stone, down to its facets and colour.
• At midnight UTC the rock is gone for good: there is no archive, by deliberate choice.
• The placard (composition, mass, temperament, provenance) is cheerful fiction, not geology.

One rock, one day, everyone

The premise is almost aggressively small. Visit todaysrock.art and a three dimensional rock sits in the centre of the screen, draggable to rotate, with a short placard and a countdown beside it. That is the entire site. There is no gallery, no feed, no login, and nothing to collect.

The quiet trick is synchronisation. According to the project's own About page, the rule is that there is only one rock at a time, generated identically for every visitor worldwide. A person in Leeds and a person in Tokyo looking at the page in the same 24 hour window are examining the same stone, not two private variations of one.

That makes the site closer to a daily event than a tool. Most generators hand each user an endless private stream of outputs. Today's Rock does the opposite: it offers a single shared object and asks everyone to agree on it for a day. The result is less a product and more a small, quiet appointment that the whole audience keeps at once.

The boundary that holds it all together is Coordinated Universal Time. The project notes explain that midnight is midnight for the artwork regardless of where the visitor lives, using UTC as one global line rather than each person's local clock. So the rock does not quietly roll over at a different moment in every timezone. It ends for everyone together.

The empty page is the frame

Most of the screen is deliberately nothing. The rock floats in a wide blank field with only its placard and a countdown for company, and that emptiness is not laziness. It is the frame. By refusing to surround the object with navigation, thumbnails, and related links, the page insists that the stone is the whole exhibit.

The effect is oddly museum like. A real display case works by isolation: one object, good light, a small card, and a lot of space telling the eye where to point. Today's Rock borrows that grammar for something as unglamorous as a pebble, and the mismatch between the reverent presentation and the humble subject is most of the joke.

The countdown is the only thing on the page that visibly moves besides the rock itself. It quietly reframes the visit as time limited, which is unusual on a web that mostly promises everything is still there whenever you get back. Here the ticking number is a gentle reminder that this particular stone has an expiry.

How the rock is generated

The interesting part is that nothing is pre made. There is no artist carving a stone each morning and no daily asset pipeline uploading a model. The rock is computed on the spot in the visitor's browser, every time, from one piece of information: today's date.

From a date to a seed

The how it works page lays out the chain plainly. The current UTC date, formatted as YYYY-MM-DD, is combined with a fixed string and run through a small hashing function called xmur3 to produce an integer. That integer becomes the seed for a pseudorandom generator called mulberry32.

Those two names are not invented for the occasion. They are well known compact routines, documented in bryc's widely cited reference on pseudorandom number generators in JavaScript. The key property is that they are deterministic: feed mulberry32 the same seed and it yields the same sequence of numbers every time, in the same order.

From there the generator stops drawing on ordinary non deterministic randomness. Every later decision, the shape, the surface noise, the colour, the placard wording, is pulled in a fixed order from that single seeded stream. Because the only input is the date plus the unchanging program, two people running the page on the same day arrive at bit for bit the same rock without ever talking to a server.

Determinism is usually a backstage virtue, the sort of thing engineers value because it makes bugs reproducible. Here it is pushed to the front and made the entire premise. The same property that lets a developer replay a failure on demand is what lets strangers across the world agree, without coordination, that they saw the one true rock of the day. It is a quiet argument that reproducibility can be an aesthetic, not just a convenience.

From a seed to a stone

Shape comes from a subdivided icosphere, a sphere approximated by many small triangles, closely related to the geodesic polyhedron. The generator then pushes each vertex in and out using deterministic three dimensional noise, so the smooth ball turns lumpy and asymmetric in a way that looks weathered rather than random.

Colour is handled with restraint. The how it works page notes the rock is given an HSL colour where saturation stays low and lightness sits around the middle, so the palette reads as stone rather than as a bright toy. The outcome is a believable grey, brown, or dull ochre pebble, never a neon gem. The constraint is doing quiet, careful work.

The placard: museum cataloguing as fiction

Beside the rock sits a small placard, and it is where the project's dry humour lives. The About page describes its text as sitting somewhere between museum cataloguing and nonsense. The fields look authoritative and are mostly made up.

Composition might read "Basalt (probably)", a label the site itself flags as intentionally fictional. Temperament might be "Stoic", which is a joke dressed as taxonomy, since a rock has no temperament to report. Provenance offers an origin story that is similarly invented. The placard performs the confidence of a natural history museum while quietly admitting it is guessing.

Mass is the one field with a number behind it. The how it works page says it is generated in roughly the 0.4 to 11.6 kilogram range and shown as an approximation. It is still a fiction, since the rock has no physical body, but it is a fiction with a plausible spread, which is exactly what makes the straight faced presentation funny.

The placard matters more than it first appears. Stripped of it, the rock would be a pleasant but mute 3D doodle. With it, the stone acquires the costume of significance: a name, a weight, a backstory, a mood. The site is gently poking at how much of an object's perceived importance comes from the label beside it rather than the thing itself, a point that lands harder because the exhibit is literally a rock.

A renderer built from scratch

The visible rock is not spun up by a heavyweight 3D engine. The making of page is candid that the site could have reached for a general purpose 3D framework and chose not to. Instead it ships a small custom renderer written for this one job.

The pipeline it describes is old fashioned and legible: generate a triangular mesh, transform it, sort its faces by depth, calculate simple lighting, and paint the result onto a canvas. That depth sort, drawing far faces before near ones, is the classic painter's algorithm, and it is enough for a single opaque lump that never needs to intersect anything else.

The painting surface is a plain 2D canvas, the drawing context documented in the MDN Canvas API. There is no WebGL, no shader program, no scene graph. The renderer fills triangles with flat shaded colour, which is why the rock has that slightly faceted, hand drawn solidity rather than a glossy photoreal finish.

The payoff of that restraint is inspectability. The making of page notes the source is public on GitHub, and a renderer this plain is something a curious visitor can actually read and understand. Keeping the dependency list near zero is not just taste, it is what lets the whole artwork remain a small readable program rather than a black box.

Why there is no archive

The decision that defines the project is the refusal to keep anything. When the UTC day ends, the rock is gone and no official record of it survives. The why no archive page states the position bluntly: the disappearance is not a missing feature, it is the feature.

The reasoning is honest about the tradeoff. An archive would make the site easier to browse, the page concedes, but it would change the central experience from discovery and immediacy into comparison and nostalgia. A scrollable back catalogue of every past rock would turn a daily event into yet another infinite feed, which is precisely the pressure the site is built to resist.

There is a neat paradox underneath it. The algorithm is fully deterministic, so in principle any past day's rock could be regenerated exactly from its date. The project declines to do so anyway. It chooses not to preserve its own history even though preserving it would be trivial, which turns impermanence into a stance rather than a limitation.

Screenshots are the one allowed exception, and they are framed as personal rather than official. A visitor can save a picture of a rock they liked, but that memento is theirs, not a canonical entry in a collection the site maintains. The artwork keeps no copy, so each rock really is seen once, by whoever showed up that day, and then let go.

Where it sits in the boring web

Today's Rock does not stand alone. Its About page places it in the Boring Websites network, described as a collection of small hand made sites that each do one particular thing and resist the usual pressure to grow larger. The rock's one a day, then gone rule is a crisp statement of that shared creed.

The family resemblance is easy to spot. Sandpile, a sibling in the same ring, runs an endless self organising avalanche of sand that likewise rewards patience over interaction. Both sites take a single idea, refuse to bolt features onto it, and trust the visitor to find the point. The wider ring, reachable through the Boring Websites hub, is full of the same discipline.

Seen as a set, these sites read as a quiet rebuttal to the engagement web. None of them want a long session, a return streak, or a growing library of your activity. Today's Rock is perhaps the purest example, since it caps the experience at one object and then throws that object away. The ambition is not to hold attention but to be worth a brief, genuine look.

Scarcity without ownership

It is tempting to file a daily generative object next to the collectible art projects that also lean on seeds and scarcity. Today's Rock pointedly does not go there. The project notes frame the rock as a shared point of agreement rather than individual possession, the opposite of generators that sell endless private, ownable outputs.

The scarcity is real but it belongs to nobody. There is exactly one rock today, which is scarce in the strict sense, yet there is no edition, no token, no way to claim it, and no resale value waiting at the end. The only thing a visitor walks away with is the memory of having looked, and perhaps a screenshot that the site treats as personal rather than canonical.

That reframes scarcity as something to experience rather than to hoard. The rock is rare the way a particular sunset is rare: everyone present can see it, nobody can keep it, and tomorrow brings a different one. It is a small, pointed answer to a web that usually treats uniqueness as a thing to be minted and traded.

How to get the most from a visit

There is no wrong way to use a site this small, but a little patience helps. Drag the rock to rotate it and look at the far side, since the deformation and lighting make the back noticeably different from whatever angle loaded first. The placard rewards a slow read once it is clear the fields are a joke told with a straight face.

Check the countdown to see how much of this rock's life is left. If a given stone is unusually lumpy, oddly coloured, or has a placard that lands well, take a screenshot, because that is the only copy that will ever exist. Then, crucially, it is worth coming back tomorrow. The entire design assumes a return visit, not a long first one.

FAQ

Does everyone really see the same rock?

Yes, within the same UTC day. The generator uses only the UTC date plus the fixed program as input, with no visitor IDs, fingerprints, or location, so every browser computes the identical stone. The rock changes for everyone together at midnight UTC.

Can I see yesterday's rock?

Not through the site. The project deliberately keeps no archive, so once a day ends its rock is gone from the page for good. The deterministic algorithm could in theory recreate any past rock from its date, but the site chooses not to, and your own screenshots are the only lasting record.

Is the rock a real photo or a 3D model?

Neither in the usual sense. It is a procedurally generated mesh, a deformed icosphere, drawn by a custom renderer that paints flat shaded triangles onto a 2D canvas. No photograph and no pre built model is involved, and the composition and mass on the placard are fiction.

Why use the browser instead of a server?

Because the date is enough. Since the rock is fully determined by the UTC date and a deterministic generator, the build needs no database and no daily upload: every visitor's browser recomputes the same specimen locally. It keeps the site light, cheap to run, and easy to inspect on GitHub.