Side-by-side benchmark comparison across knowledge, coding, math, and reasoning.
Sibling matchup inside the o1 family.
o1-preview and o1 sit in the same o1 family. This page is less about two unrelated model lineages and more about how the siblings trade off on benchmark shape, token costs, and practical limits like context window.
o1-preview is clearly ahead on the aggregate, 83 to 51. The gap is large enough that you do not need to squint at the spreadsheet to see the difference.
o1-preview's sharpest advantage is in coding, where it averages 70.3 against 41. The single biggest benchmark swing on the page is SWE-bench Verified, 65 to 41. o1 does hit back in knowledge, so the answer changes if that is the part of the workload you care about most.
o1-preview makes more sense if coding is the priority, while o1 is the cleaner fit if knowledge is the priority.
o1-preview
78
o1
83.8
o1-preview
70.3
o1
41
o1-preview
93.1
o1
74.3
o1-preview
88
o1
92.2
o1-preview and o1 are sibling variants in the o1 family, so the right pick depends on whether you value the better benchmark line, cheaper tokens, or the larger context window. o1-preview is ahead overall 83 to 51.
o1 has the edge for knowledge tasks in this comparison, averaging 83.8 versus 78. Inside this category, GPQA is the benchmark that creates the most daylight between them.
o1-preview has the edge for coding in this comparison, averaging 70.3 versus 41. Inside this category, SWE-bench Verified is the benchmark that creates the most daylight between them.
o1-preview has the edge for math in this comparison, averaging 93.1 versus 74.3. Inside this category, AIME 2024 is the benchmark that creates the most daylight between them.
o1 has the edge for instruction following in this comparison, averaging 92.2 versus 88. Inside this category, IFEval is the benchmark that creates the most daylight between them.
Get notified when new models drop, benchmark scores change, or the leaderboard shifts. One email per week.
Free. No spam. Unsubscribe anytime. We only store derived location metadata for consent routing.