The AI Reader.
The Mechanics

Ask an image generator for 3:15 and it hands back a clock at 10:10

The watches in its training data almost all point at ten and two, and nothing in the generator turns a requested time into an angle.

Why this matters

Image generators are in ordinary hands now, and one of the quickest ways to catch one not understanding what it draws is to ask for a specific time. Request a watch at 3:15 and it returns 10:10; ask a model to read the time off a photo of a clock and it often misses too. Both are easy to wave away as the tool being bad at clocks. By the end of this you will be able to say what actually produces the behavior and name the two separate things behind it. You will also be able to use them to predict other places where a model draws the most familiar version of something instead of the one you asked for.

Background optional reading
01
An image generator turns a field of static into your picture by removing the noise a little at a time: how a diffusion generator works, the process this behavior sits on top of.
02
A chatbot slices your photo into a few hundred squares and turns each into a word: how a model reads an image it is handed, the reverse task in the last section.

A watch drawn to order still reads 10:10

Ask an image generator for a wristwatch showing 3:15. Almost always, it hands back a watch reading close to 10:10, both hands raised toward the top of the dial, one near the 10 and one near the 2. Ask for 7:20 and you get the same face. The pull is strongest for wristwatches and watch-like faces. Wall clocks come out at more varied times.1

A reasonable guess is that the model read the words 3:15, worked out where the hour and minute hands belong, and drew them roughly there. That is not what happens. Nothing inside the generator ever converts 3:15 into the position of two hands.

The generator renders the most likely clock

A diffusion image generator does not draw a clock the way a person would, by choosing a time and placing each hand to show it. It begins with a field of random static and takes the noise away a little at a time until a picture remains, a process explained in full in An image generator turns a field of static into your picture. What matters here is the single thing the model was trained to do. Its training rewards one outcome: producing images whose statistics match the images it was shown. The paper that introduced these models describes the goal as a chain trained to produce samples matching the data after a finite number of steps.2 Nothing in that objective rewards a rule that applies to a single image, such as make the hands show the requested time. It rewards looking like the data in aggregate.

That turns the question of what the model draws into a question about what it saw. A clock it renders will look like the clocks in its training images, in whatever way those clocks tended to look.

Ten past ten is a sales pose

Clocks and watches in photographs are not posed at random times. Since the 1950s, watch advertisements have set the hands at 10:10, where the decades before favored 8:20.3 Two forces hold the convention in place. The raised hands frame the maker's logo, which usually sits just below the 12, so 10:10 keeps the brand name clear.4 And the two lifted hands read as a smiling face. In a controlled study, viewers shown a watch at 10:10 reported more pleasure than the same watch at 11:30 and rated the 10:10 face as resembling a smile. The pose also raised their stated intention to buy, and it did so without their noticing.3

No one has counted the times shown on clocks across a training set the size these models use, so this is an inference rather than a tally. What is documented is the convention and the fact that product and stock photography, which make up the bulk of clock and watch imagery online, follow it.1 The well-supported inference is that the faces the model saw lean heavily toward 10:10, binding the idea of a watch to hands near the 10 and the 2. The binding is tightest for watches. In one documented test, a generator asked for watches returned 10:10 almost every time, while the wall clocks it drew came out at scattered times.1

Nothing turns 3:15 into two hand angles

A text prompt does change what the model draws. The words 3:15 enter the same way the word watch does, as a description the denoising is steered toward. But the model can only make the image look like a watch, and the watches it learned from look like 10:10. It has no separate step that reads 3:15, works out that the minute hand should point straight down and the hour hand a quarter of the way past the 3, and places them there. That computation was never part of what training rewarded, so the model never built it.

This is a sharper failure than a model simply being bad at detail. When a generator draws the wrong number of apples, it is missing one count. The same kind of gap turns up in an image generator turning "six apples" into "some apples" and in an image generator never counting the fingers it draws. The clock combines two specific gaps at once: a training set that leans hard toward one arrangement, and the absence of any rule connecting a requested time to an angle. It is the single-mode version of a pattern already seen in text, where a chatbot asked for a random number tends to answer 7, drawing from a lopsided distribution it learned rather than from any source of chance. The clock has one dominant answer where the random number had a few.

The pull toward 10:10 is strong enough to surface even when a model is asked to read a clock rather than draw one. On a benchmark of instrument reading, one open model answered 10:10 for 72.88% of the real clock photographs it was asked to read, regardless of the time the hands actually showed.5

The pose leaks into reading
"many models tend to answer '10:10' when reading clock times, regardless of the actual time shown in the image."5 MeasureBench, reading the default as the advertising pose

The behavior is not fixed, and it is coming apart model by model. A documented test in August 2026 ran one prompt, a request for wall clocks reading 3:27, through ten image generators.6 Several still produced 10:10. One, GPT Image 2, placed every minute hand at :27 and the hour hands within about six minutes of correct. That is a demonstration rather than a measured study, and it cannot say what changed: more clock-specific training images, an added planning or tool step, or a different design would all look the same from the outside. What it shows is that the missing rule is becoming a solved problem in some systems and not others.

Reading a clock face hits the same missing step

The reading failure is the same absence seen from the other side. A vision-language model handed a photograph of a clock has to turn two hand angles back into a time, the task laid out in a chatbot slicing your photo into squares and turning each into a word. It was no more trained to compute angle-to-time than the generator was to compute time-to-angle, so it stumbles on a task most people find trivial. On ClockBench, a set of 720 questions about analog faces, people score 90.7% and the best model shown scores 66.7%.7 At the benchmark's launch in September 2025, the best model managed 13.3%, missing by a median of about an hour where people missed by about three minutes.8

That climb from 13.3% to 66.7% in a year is the part still in motion, and some of the movement is deliberate. On a set of 12,483 real-world clock photos, a base model read the full time correctly 1.41% of the time. After training aimed squarely at the habit of swapping the hour and minute hands, the same model reached 46.22%.9

Two measures of analog-clock reading. Humans score 90.7% on ClockBench; the ClockBench figures are the best model shown at launch and now, and the TickTockVQA pair is one base model before and after targeted tuning.789
Reading task Worse score Better score What changed
ClockBench, best model 13.3% 66.7% Newer general-purpose models, about a year apart.
TickTockVQA, one base model 1.41% 46.22% Tuning aimed at the hour-and-minute-hand swap.

That marks the line between what is settled and what is open. Settled: a diffusion model reproduces the statistics of its training images, and clock imagery leans toward one pose. Open: how far targeted data or an added tool closes the gap, and whether models that plan their reading or call a clock-reading tool clear it entirely. A watch coming back at 10:10 is the settled part on display. Whether a model can be made to draw or read the time you actually asked for is the part still being decided, system by system.

The takeaway

So 10:10 is not the tool being bad at clocks. It is two ordinary things at once. The clocks and watches it learned from almost all point at ten and two, so that is the face it treats as normal. And it was never given a step that turns a requested time into the angle of two hands, so the words 3:15 have nothing to act on. The same missing step, run the other way, is why reading an arbitrary clock is hard. The useful part is that this predicts where else it happens. Wherever the correct answer depends on a rule the training pictures never taught, and a single familiar arrangement crowds the data, a generator will hand back the familiar arrangement and not the one you asked for. The clock is only the cleanest case to see it in.

Go deeper optional reading
01
ClockBench: the reading benchmark itself, with analog faces you can try against the models' scores.
02
Mechanical Watch: an interactive account of how a real watch's gears turn a wound spring into the exact hand angles a generator has no rule for.

Sources

  1. Digital Camera World · Mike Harris, "Why are AI-generated images of clocks always set to 10 past 10?"
  2. arXiv · Ho, Jain & Abbeel, "Denoising Diffusion Probabilistic Models"
  3. Frontiers in Psychology · Karim et al., "The Role of Watch Advertisement Time Setting in Consumer Preference"
  4. PetaPixel · Jaron Schneider, "The Science Behind Why Watches Are Set to 10:10 in Advertising Photos"
  5. arXiv · BAAI FlagEval Team, "MeasureBench: Reading Measurement Instruments"
  6. Polymath07 · "Getting Clocks Right: AI Almost There"
  7. ClockBench · Alek Safar, analog-clock reading benchmark
  8. The Decoder · Jonathan Kemper, "Even the best AI models can't reliably read the clock"
  9. arXiv · Choi, Lee, You & Lee, "TickTockVQA and Swap-DPO"