Papers › Fashion-MNIST: a Novel Image Dataset for Benchmarking Machine Learning Algorithms

Fashion-MNIST: a Novel Image Dataset for Benchmarking Machine Learning Algorithms

25 Aug 2017arXiv:1708.07747archive 2025-07-28

Han Xiao, Kashif Rasul, Roland Vollgraf

We present Fashion-MNIST, a new dataset comprising of 28x28 grayscale images of 70,000 fashion products from 10 categories, with 7,000 images per category. The training set has 60,000 images and the test set has 10,000 images. Fashion-MNIST is intended to serve as a direct drop-in replacement for the original MNIST dataset for benchmarking machine learning algorithms, as it shares the same image size, data format and the structure of training and testing splits. The dataset is freely available at https://github.com/zalandoresearch/fashion-mnist

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 1 code sample harvested from 1 repository linked to this paper: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: official repository: 1 sample from 1 repository, 1 ran (0 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 4 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

37 repositories listed; official and paper-mentioned ones first.

zalandoresearch/fashion-mnist officialmentioned in papermentioned on GitHubtfSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
AFAgarap/cnn-svm mentioned on GitHubtfSyntology: not harvested report
GeorgiosSmyrnis/multiclass_minimization_icml2020 mentioned on GitHubtfSyntology: not harvested report
Hitsaa/Practice mentioned on GitHubtfSyntology: not harvested report
Jerold25/Gradient-Descent-Optimization mentioned on GitHubSyntology: not harvested report
SeventeenChen/fashionMNIST_CNN_master mentioned on GitHubpytorchSyntology: not harvested report
SeventeenChen/fashionMNIST_LeNet_master mentioned on GitHubpytorchSyntology: not harvested report
SeventeenChen/fashionMNIST_ResNet_master mentioned on GitHubpytorchSyntology: not harvested report
Sivaneshmsc/FashionMNIST mentioned on GitHubtfSyntology: not harvested report
WilliamLiPro/LpSS mentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
WilliamPeng38/Fashion mentioned on GitHubtfSyntology: not harvested report
Zernach/Fashion-MNIST mentioned on GitHubtfSyntology: not harvested report
akulkailwoo/zalando-fashion-mnist mentioned on GitHubtfSyntology: not harvested report
ayeshakhtar209/fashion-mnist mentioned on GitHubtfSyntology: not harvested report
balamurugan0714/TensorFlow mentioned on GitHubtfSyntology: not harvested report
coMindOrg/federated-averaging-tutorials mentioned on GitHubtfSyntology: not harvested report
dhifoster/msc-birkbeck-ml-cwk mentioned on GitHubtfSyntology: not harvested report
edgarjimenez1996/-fashion-mnist mentioned on GitHubtfSyntology: not harvested report
errec-sun/mnist mentioned on GitHubtfSyntology: not harvested report
facebookresearch/disentangling-correlated-factors mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Disentanglement of Correlated Factors via Hausdorff Factorized Support (arXiv:2210.07347; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
gabrieldewetLM/ml-demo mentioned on GitHubtfSyntology: not harvested report
guillempla/Fashion-MNIST-Neural-Network mentioned on GitHubSyntology: not harvested report
harshit17chaudhary/SML_assignment_1 mentioned on GitHubtfSyntology: not harvested report
huckiyang/MOT-Kuzushiji-Fashion-Video mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Deep Learning for Classical Japanese Literature (arXiv:1812.01718; that paper's own run record: 8 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 1 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified); nothing checks that they implement this paper's method. report
jkcrosby3/FashionMNST mentioned on GitHubtfSyntology: not harvested report
michaelaerni/interpolation_robustness mentioned on GitHubjaxSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Interpolation can hurt robust generalization even when there is no noise (arXiv:2108.02883; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
qampspring2023/qgpt-issue-31 mentioned on GitHubSyntology: not harvested report
robertsenps/data mentioned on GitHubtfSyntology: not harvested report
rwaithaka/testdrive2 mentioned on GitHubtfSyntology: not harvested report
saeedmhz/Mechanical-MNIST-Crack-Path mentioned on GitHubSyntology: not harvested report
sandeepreddy06/fashion-mnist mentioned on GitHubtfSyntology: not harvested report
smurthy2020/fashion mentioned on GitHubtfSyntology: not harvested report
sriloksagar/fashion-mnist mentioned on GitHubtfSyntology: not harvested report
takashiishida/irreducible mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Is the Performance of My Deep Network Too Good to Be True? A Direct Approach to... (arXiv:2202.00395; that paper's own run record: 0 ran · 1 unverified); nothing checks that they implement this paper's method. report
udaydutt12/Neural-Nets mentioned on GitHubtfSyntology: not harvested report
zsk66/flame mentioned on GitHubpytorchSyntology: not harvested report
JoegameZhou/MNIST_Example mindsporeSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

1 sample harvested: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong

Licence: 0 of the 1 sample are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from zalandoresearch/fashion-mnist. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

zalandoresearch/fashion-mnist official repository 1 sample, 1 ran (1 instrument-failed) · 0 unverified
load_mnist in 35 papers utils/mnist_reader.py ran · our draft was wrong MIT (permissive) · fcde486b88e624a8 · report fixture: signature path:str/0/str, kind:str/0/str · returned tuple · level recorded 2026-09-22

Tasks

BIG-bench Machine LearningBenchmarking

Datasets

Introduced by this paper, per the archive.

Fashion-MNIST

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections