Stanford Cars Dataset (HuggingFace)
Datadory delivers Stanford Cars dataset HuggingFace data for automobile manufacturers teams: 16,185 labeled car photographs spanning 196 make-model-body style-year classes from more than 49 manufacturers, from AM General Hummer SUV 2000 to Tesla Model S Sedan 2012. Every image carries one verified class label, and seven corruption variants of the test set ride along for robustness work.
What is the Stanford Cars Dataset on HuggingFace?
A fine-grained visual classification benchmark where every photograph is one specific vehicle, not just "a car." The canonical split holds 8,144 training and 8,041 test images across 196 classes, each class a Make Model Body Style Year string - AM General Hummer SUV 2000 at one end of the alphabet, smart fortwo Convertible 2012 at the other, with Audi, BMW, Ferrari, Mercedes-Benz, Tesla, Toyota, Volkswagen and Volvo among the 49+ manufacturers in between. This mirror packages the benchmark in parquet alongside seven corrupted variants of the test set, lifting total rows to 72,472.
Why automobile manufacturer teams care: the labels resolve at trim-and-model-year precision. A model that separates Tesla Model S Sedan 2012 from an Acura RL Sedan 2012 has already done the hard part of competitive visual intelligence - identifying exactly which product a customer photographed, parked down the street, or listed for sale. Registration counts tell you how many vehicles exist; this tells you what one specific vehicle looks like from the outside, labeled.
Datadory delivers it as a working dataset: images paired with integer label indices into the 196-class name list, ready to join against any make-model table your organization already maintains.
What does a sample row look like?
Two columns per row - the photograph itself and its position in the label space. Four representative rows:
label : 0
name : AM General Hummer SUV 2000
label : 12
name : Audi TTS Coupe 2012
label : 100
name : Ferrari FF Coupe 2012
label : 184
name : Tesla Model S Sedan 2012Each label is an integer index into a fixed 196-entry list of class names, so decoding a prediction is one array lookup, never a fuzzy string match. The paired images are variable-resolution consumer photography - anywhere from 78 px to 5.62k px wide - worth knowing before you pick input sizes: the benchmark rewards models that handle real-world framing, not studio shots.
What fields does the dataset include?
Two documented fields, verified against the mirror card. The schema is deliberately minimal - the information lives in the pixels and in the 196-entry label-name array, not in extra metadata columns.
What does coverage look like across geography, time and granularity?
Geography - not geographically scoped: consumer vehicle photography skewed toward US-market models, so treat it as North American showroom reality rather than a global fleet census.
Temporal - a static benchmark rather than an ongoing series. Vehicle model years run roughly 1991 through 2012, which captures the era when most current nameplates took their modern shape; the mirror copy was last modified May 2, 2024.
Granularity - one row per image at make/model/body-style/year resolution. Splits: 8,144 train, 8,041 test, plus seven corrupted test variants of 8,041 each (contrast, gaussian noise, impulse noise, JPEG compression, motion blur, pixelate, spatter) - nine parquet splits totaling 72,472 rows.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
Who uses this data, and for what?
- Model benchmarking - the canonical train/test split lets computer-vision teams compare their fine-grained classifier against published results instead of a private eval set nobody else can check.
- Robustness testing - the seven corruption variants (blur, noise, compression artifacts, weather occlusion) simulate what happens to a recognition model when photos arrive from a cracked phone camera or a rain-soaked lot camera.
- Dealer inventory and listing automation - train make-model-year recognition on the benchmark, then tag incoming trade-in or listing photos automatically instead of hand-keying trims.
- Insurance photo triage - identify the exact vehicle in a claim photo before an adjuster opens the file; year-level labels matter because parts pricing differs across design generations.
- Competitive visual audits - track which competitor models appear in street photography or marketing imagery, at nameplate precision rather than generic sedan-versus-SUV buckets.
Which personas get the most value?
Data scientists and ML engineers get a labeled, split-fixed benchmark whose 196-class label space is small enough to sanity-check by eye and hard enough to expose weak models. Developers building data products get two-column parquet that loads into any dataframe library without schema archaeology. Product managers in automotive software get a defensible answer to "can we recognize the car in this photo?" before budgeting a collection effort. Market researchers and consultants get citable class definitions - 49+ manufacturers enumerated at model-year level - for reports on vehicle segmentation.
What should I know before requesting a sample?
Three things worth knowing upfront. First, mind the row-count trap: the canonical benchmark is 16,185 images (8,144 + 8,041); the mirror's corrupted variants push total rows to 72,472, so quote whichever figure matches whether you mean benchmark accuracy or raw row volume. Second, no license is declared on the mirror card and the original benchmark circulated for research purposes - confirm permitted use for commercial application during the sample conversation rather than after deployment. Third, image resolutions vary widely (78 px to 5.62k px wide), so settle preprocessing policy around the low end if your pipeline assumes uniform inputs.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| field | type | definition | example |
|---|---|---|---|
image | image | Car photograph stored as an image feature with variable resolution, from 78 px up to 5.62k px wide; consumer-quality framing rather than studio shots. | front three-quarter view of a sedan |
label | integer | Class index into the fixed 196-entry list of Make Model Body Style Year strings; decode predictions with one array lookup. | 184 = Tesla Model S Sedan 2012 |
Coverage at a glance
| dimension | value |
|---|---|
| Geography | Not geographically scoped; consumer vehicle photography, primarily US-market models |
| Temporal | Static benchmark; model years circa 1991-2012, mirror last modified May 2, 2024 |
| Granularity | One row per image; 196 make/model/body-style/year classes; 8,144 train + 8,041 test + 7 corruption variants of 8,041 each |
Questions buyers ask
How many classes does the Stanford Cars dataset have?
196 classes, each a Make Model Body Style Year combination such as Audi TTS Coupe 2012 or Ferrari FF Coupe 2012. Classes span more than 49 manufacturers, which is what makes the label space fine-grained: several classes differ only by body style or model year within the same make.
How many images are in the dataset?
16,185 in the canonical split - 8,144 training and 8,041 test. This mirror adds seven corrupted test-set variants at 8,041 images each, bringing total rows across nine parquet splits to 72,472. Quote 16,185 for benchmark comparisons and 72,472 only when counting every variant.
Can I use this data commercially?
Tell us the intended use with your sample request and we confirm the terms that apply before delivery. The original benchmark circulated in research settings, so the honest answer depends on your application - which is exactly why it gets settled during scoping rather than after deployment.
Does it include vehicles newer than 2012?
No - the newest class is smart fortwo Convertible 2012 and model years reach back roughly to 1991. For post-2012 nameplates pair this benchmark with a complementary feed; the label taxonomy still transfers because most current nameplates kept their shape across that boundary.
What makes this dataset hard for models?
Fine-grained boundaries: an Audi S4 Sedan 2007 versus an Audi S6 Sedan 2011 differ by subtle grille and lamp signatures, not silhouette. The seven corruption variants then compound the difficulty with blur, noise, compression and weather effects - the gap between clean and corrupted accuracy is your robustness scorecard.
How do I get a sample of this dataset?
Use the Get a sample form and state your intended task - classification benchmark, inventory tagging, or robustness evaluation - plus the split you want to inspect. Samples arrive as a manageable subset of labeled rows so class balance and image quality can be verified before the full delivery lands.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.