in Blog

January 21, 2026

Machine Learning Datasets

Author:




Artur Haponik

CEO & Co-Founder


Reading time:




13 minutes


Key Takeaways

  • Machine learning datasets can come from two main sources: data your organization already owns, or public/open datasets available online.
  • The four largest sources of public ML datasets are UCI ML Repository (curated, academic), Google Dataset Search (broadest reach), Kaggle (400,000+ community datasets), and Hugging Face Datasets (250,000+, dominant for NLP and deep learning).
  • A good dataset is relevant, well-labeled, properly licensed, and free of unintended bias — quality matters more than raw size.
  • In 2026, synthetic data and LLM-generated data have become mainstream alternatives when public datasets don’t fit or privacy rules block real data.
  • For most business ML projects, the dataset is the constraint — not the algorithm. Spend at least as much time vetting data as choosing the model.

As you know from our previous article, the entire idea behind machine learning is to go from data to insight. No matter what type or kind of project you plan to conduct, you always need datasets for machine learning projects. Your algorithm has to have a base to learn from and gain the necessary information. Thankfully, there are tons of datasets for machine learning projects. Many of them are available for free, from open sources.

You can obtain machine learning datasets in two ways. First, if you work for a client, they can provide you with the dataset you need. Such a dataset can consist of, for instance, the list of orders, data from Google Analytics, past financial results, and other operational data. In such a situation, the company itself is a source of the necessary dataset. Things get complicated when you need a dataset you don’t possess. Then, there is the second option–public-available datasets. You’d be surprised how many of them are just at hand, on the Internet! But before we switch to that, let’s talk for a moment about a perfect dataset. As it turns out, not every dataset will be usable, not to mention suitable for the given project.

The datasets for machine learning projects

When deciding which dataset ought to be used, follow two simple rules:

  • Search for datasets with relevant information
  • Search for datasets of high quality

Why is this approach crucial? The reasons are also twofold. First, if you input irrelevant data to your AI algorithm, not only will you receive a distorted outcome, but, in many instances, no outcome at all. Second, a high-quality database makes efficient work accessible. If the algorithm has to plough through unnecessary data instead of doing its job, the whole process will take much longer. No one wants to fight with useless information, and machine learning algorithms are no exception.

So, what does the high-quality dataset look like? First, high-quality dataset should not be messy or filled with too much information. You do not want to spend a lot of time cleaning and selecting data, or deleting unnecessary columns and rows. Keep it simple–concentrate only on relevant information. Second, always have your goal in mind. You should have a question or decision to answer, which in turn can be answered with the data you possess.

How to find relevant datasets?

How to find relevant datasets?

There are over hundreds of various datasets containing hundreds of megabytes of information. Thankfully, you don’t have to search through them manually. There are three useful dataset finders/aggregators, which can do that for you.

The UCI ML repository

The UCI Machine Learning Repository is owned by the University of California, School of Information and Computer Science. It currently hosts over 600 publicly available datasets, specifically for machine learning and data analysis. The UCI Machine Learning Repository is a collection of databases, domain theories, and data generators that are used by the machine learning community for the empirical analysis of machine learning algorithms. The archive was created as an FTP archive in 1987 by David Aha and fellow graduate students. Since that time, it has been widely used by students, educators, and researchers all over the world as a primary source of machine learning datasets[1].

The datasets within UCI finder are tagged with specific categories, e.g. classification or regression, in order to help you practice given ML technique. The vast majority of the datasets within UCI come from the real world.

Google dataset search

In late 2018, Google launched its own finder (they call it “the toolbox”) that can search for datasets by name. Even though it’s still in the BETA phase, it is fully operational, and you can find it here.

Google Dataset Search allows you to look for the datasets available on the Internet using given keywords. This search engine obtains information about datasets stored in thousands of online repositories.

Google Dataset Search, tablet

Kaggle

Kaggle is another outstanding resource for machine learning datasets. Compared to UCI, it’s simply enormous. It contains over 400,000 public datasets as of 2026 — and a community of more than 20 million users. Kaggle is not merely a search engine. It is an online community of data scientists and machine learning specialists, where you can have a discussion about data, find some public code or even create your own projects. Kaggle allows users to find and publish machine learning datasets, explore and build models in a web-based data-science environment, work with other data scientists and machine learning engineers, and enter competitions to solve the data science challenges. Currently, it has over 1 million users in almost 200 countries[2]. What’s interesting, Google acquired Kaggle in 2017.

Obviously, this doesn’t limit your searching possibilities. You can explore hundreds of different machine learning datasets available on the Internet. Many of them are related to the specific discipline or industry, but the range of available databases is so much wider! We will examine some public datasets for machine learning. Let’s begin with the various government machine learning datasets.

Hugging Face Datasets

Hugging Face has become the de facto standard repository for machine learning datasets in the deep learning era. The platform hosts over 250,000 public datasets as of 2026, with particularly deep coverage of:

  • NLP and LLM training data — text corpora, instruction-tuning sets, RLHF preference data
  • Computer vision — image classification, segmentation, multimodal vision-language sets
  • Audio and speech — for ASR, TTS, and audio classification
  • Tabular and time-series — for classical ML use cases

What sets Hugging Face apart from older repositories is its tight integration with model training: the datasets Python library lets you stream a dataset directly into a training loop in two lines of code, without downloading the full archive. It’s also become the natural home for datasets created or curated by the open-source AI community.

Repository Best for Approx. number of datasets (2026) Strengths Limitations
UCI ML Repository Learning, classical ML benchmarks 600+ Curated, well-documented, ideal for teaching Mostly small, tabular, older datasets
Google Dataset Search Finding any dataset on the web Millions indexed Broadest reach, search across thousands of sources Quality varies; you need to vet each source
Kaggle Real-world problems, competitions, community 400,000+ Active community, notebooks, code examples Many datasets are user-uploaded — quality varies
Hugging Face Datasets NLP, computer vision, LLM training 250,000+ Streaming API, deep learning-ready, vibrant OSS community Less coverage of classical ML / tabular

The public and open datasets for machine learning

A variety of governments and international organizations freely share their machine learning datasets, and most of them can be downloaded free of charge, directly from their websites. Consider a couple of interesting open machine learning datasets for machine learning provided by various governments and organizations.

laptop, typing, ML datasets

Data.gov

This is a vast US machine learning datasets base, managed and hosted by the US General Services Administration, Technology Transformation Service. Data.gov hosts over 300,000 datasets as of 2026, representing tens of millions of underlying data resources. They represent about 10 million data resources. This is an unimaginable number!

You can search Data.gov from its catalog of government data. The searching process and quite simple and based on keywords. Obtained results can be browsed through types, tags, formats, groups, organization types, organizations, and categories.

EU open data portal

This is the second, fascinating catalog comprising thousands of machine learning datasets for machine learning projects. What’s interesting, all data within this catalog is free to use and reuse, even for commercial purposes! You can browse datasets by subject or groups. There are nine primary subjects: Agriculture, fisheries, forestry and food, economy and finance, education, culture and sport, energy, environment, government and public sector, health, international issues, justice, legal system, and public safety.

A similar portal is called Eurostat (ec.europa.eu/Eurostat). This is the statistical office of the European Union[3]. Eurostat’s key task is to “provide the European Union with statistics at European level that enable comparisons between countries and regions.” Here, you can also browse databases by themes, for instance, economy and finance, population and social conditions, industry, trade, and services, science, technology, or international trade.

These are the two most interesting government datasets. Apart from them, you can also find the datasets catalogs from the following countries:

  • New Zealand: data.govt.nz
  • India: data.gov.in
  • Northern Ireland: opendatani.gov.uk

The datasets for machine translation

This is another interesting example of machine learning datasets. The machine translation applications work on a similar to machine learning basis. The MT software translates a text from the source language into the target language, all on its own. To make that possible, these applications use massive databases containing hundreds of millions of words, phrases, and expressions as the source they can base on.

With this source accessible, the MT applications can “decide”, which translation method is the most appropriate and accurate.

The datasets for machine translation

One of the most modern and complex MT systems in the world is Microsoft Translator[4]. Initially, it was based entirely on the Statistical Machine Translation (SMT) method, which means that it was searching for the most probable translation–statistically, the most frequently found in its database. This is a good place for a small digression–what exactly is in such a database? The simplest example–the entire Wikipedia entry database[5]. And how much is that? Well, as it turns out, 27 billion words in 40 million articles in 293 languages[6].

Today, Microsoft has fully migrated to Neural Machine Translation (NMT) — a deep learning approach that translates entire sentences as a single unit, using the full context rather than translating word by word. Modern NMT, and its successors built on transformer architectures (the same family that powers ChatGPT, Claude, and Gemini), have dramatically improved translation quality across more than 100 languages. Statistical machine translation, the previous standard, is now largely historical.

How to evaluate dataset quality?

Before downloading a dataset, run it through a quick checklist. A poorly chosen dataset can sink an ML project before it starts.

  • Relevance. Does the dataset actually represent the problem you’re trying to solve? A facial recognition dataset of only one demographic won’t generalize. A retail dataset from a different country may not reflect your market.
  • Size and class balance. Is there enough data to train meaningfully, and is it balanced across the classes you care about? An imbalanced dataset (say, 99% non-fraud and 1% fraud) needs special handling.
  • Labels and ground truth. Are labels accurate, consistent, and well-documented? Look for a labeling guide or annotation methodology — if there isn’t one, treat the labels with caution.
  • Provenance and license. Who created it, when, and how? Is the license suitable for your use case — academic, commercial, or both? Datasets without a clear license shouldn’t be used in production.
  • Bias and representativeness. Does the data reflect the population your model will encounter? Models trained on biased data produce biased predictions — and that’s a legal and reputational risk in regulated industries.
  • Privacy and PII. Especially in healthcare, finance, or HR datasets — has personally identifiable information been properly removed or anonymized?
  • Documentation. A good dataset comes with a “dataset card” or README describing collection methods, known issues, and recommended use cases. Hugging Face and Kaggle have standardized this format.

A useful rule of thumb: spend at least as much time evaluating a dataset as you would evaluating a vendor. The model you build is only as good as the data underneath it.

When public datasets aren’t enough: synthetic and LLM-generated data?

Sometimes the dataset you need simply doesn’t exist publicly — or what exists doesn’t match your domain. In 2026, two newer options have become mainstream:

  • Synthetic data generation. Tools like Gretel, Mostly AI, and Synthetic Data Vault can generate statistically realistic but fully artificial data — useful when privacy regulations block access to real records (healthcare, finance, HR), or when you need more examples of a rare event for training.
  • LLM-generated training data. Large language models can be used to generate labeled text data for fine-tuning smaller, task-specific models. This is now a common pattern for chatbots, classifiers and intent detection systems, where collecting and labeling real data would take months.

Both approaches require careful validation — synthetic data can preserve or even amplify biases from the source distribution, and LLM-generated data can encode the generating model’s blind spots. Used well, though, they have made it possible to train production-grade models with far less real-world data than was needed five years ago.

Other public machine learning datasets

When thinking of possible machine learning datasets for your projects, you are literally spoiled for choice. There are available various machine learning datasets for almost every field, discipline, and industry. We have a couple of interesting machine learning datasets examples.

  • Finance and economics: Nasdaq Data Link (formerly Quandl) — data.nasdaq.com
  • Satellite imagery: xView — xviewdataset.org
  • Autonomous driving: Waymo Open Dataset, nuScenes, Argoverse
  • Healthcare and clinical: MIMIC — physionet.org/content/mimiciv
  • Face recognition: SCFace, CelebA, LFW
  • Vision and object detection: Visual Genome — visualgenome.org, COCO — cocodataset.org, Open Images
  • Handwriting: MNIST
  • Email and text: Enron Email Dataset
  • Music and audio: Million Song Dataset — millionsongdataset.com, AudioSet — research.google.com/audioset

And many, many more. For instance, you can see over 300 datasets, grouped into different categories here.

As you can see, there’s no shortage of public machine learning datasets — across academic repositories, community platforms, government portals, and increasingly synthetic or LLM-generated sources. The real challenge isn’t finding data, it’s choosing data that fits your specific problem, validating its quality, and combining public sources with your own proprietary data where it matters most.

In our own work at Addepto, we usually start from a client’s internal data — operational records, customer interactions, sensor readings — and supplement it with public datasets only where they genuinely strengthen the model. The most successful ML projects we’ve seen are rarely the ones with the largest dataset; they’re the ones where the data was carefully matched to the problem.

If you’d like help mapping the right datasets — public, private, or synthetic — to a real business problem, book a 30-minute call with our team.

References

[1] UCI. Machine Learning Repository. URL: https://archive.ics.uci.edu/ml/about.html. Accessed Jan 21, 2020.
[2] Wikipedia. Kaggle. URL: https://en.wikipedia.org/wiki/Kaggle. Accessed Jan 21, 2020.
[3] Europa. Eurostat. URL: https://ec.europa.eu/eurostat/about/overview. Accessed Jan 21, 2020.
[4] Microsoft. Machine Translation. URL: https://www.microsoft.com/en-us/translator/business/machine-translation/. Accessed Jan 21, 2020.
[5] Wikipedia. Wikipedia:Database download. URL: https://en.wikipedia.org/wiki/Wikipedia:Database_download. Accessed Jan 21, 2020.
[6] Wikipedia. Wikipedia:Size comparisons. URL: https://en.wikipedia.org/wiki/Wikipedia:Size_comparisons. Accessed Jan 21, 2020.


FAQ


What is a machine learning dataset?

plus-icon minus-icon

A machine learning dataset is a structured collection of examples used to train, validate, or test an ML model. It can contain text, images, audio, video, tabular data, or any combination — together with labels or annotations that describe what the model should learn to predict.


Where can I find free machine learning datasets?

plus-icon minus-icon

The four largest sources are the UCI ML Repository (curated academic datasets), Google Dataset Search (search engine across the open web), Kaggle (community-driven, with 400,000+ datasets), and Hugging Face Datasets (250,000+ datasets, particularly strong for NLP and deep learning). Many governments also publish open data — Data.gov, the EU Open Data Portal, and others.


What makes a good machine learning dataset?

plus-icon minus-icon

A good dataset is relevant to the problem, large enough to train meaningfully, well-labeled with documented annotation methodology, free of obvious bias against the target population, properly licensed for your use case, and comes with a clear “dataset card” describing how it was collected and known limitations.


How much data do I need to train a machine learning model?

plus-icon minus-icon

It depends entirely on the task. Simple tabular classification can work with a few thousand examples. Computer vision usually needs tens of thousands. Training a large language model from scratch needs hundreds of billions of tokens — which is why almost no one trains LLMs from scratch; instead, they fine-tune existing models on small task-specific datasets (often just a few hundred or thousand examples).


What's the difference between training, validation, and test datasets?

plus-icon minus-icon

The training set is what the model learns from. The validation set is held out during training and used to tune hyperparameters and detect overfitting. The test set is used only at the very end, to measure how well the final model generalizes to unseen data. A common split is 70/15/15 or 80/10/10, though for very large datasets a smaller percentage for validation and test is fine.


Can I use public datasets for commercial projects?

plus-icon minus-icon

Not always. Each dataset has a license — some allow commercial use (e.g., CC-BY, MIT), some restrict use to research or non-commercial purposes (e.g., CC-BY-NC), and some have no clear license at all. Always check before building a commercial product on top of a public dataset, and document your choice for compliance.


What is synthetic data, and when should I use it?

plus-icon minus-icon

Synthetic data is artificially generated data that mimics the statistical properties of real data without containing actual records. It’s useful when privacy regulations block real data (healthcare, finance), when you need more examples of rare events for training, or when collecting real labeled data is too slow or expensive. The trade-off is that synthetic data can preserve biases from its source — it always needs validation.


What's the difference between a dataset and a database?

plus-icon minus-icon

A database is a system designed to store, query, and update structured data over time (e.g., PostgreSQL, MongoDB). A dataset is a static, point-in-time snapshot of data, usually exported as CSV, Parquet, JSON or similar — designed to be read for analysis or model training, not continuously updated. ML projects usually start by extracting a dataset from a database.




Category:


Machine Learning