HuggingFaceFW/fineweb

🍷 FineWeb

<center> <img src="https://huggingface.co/datasets/HuggingFaceFW/admin/resolve/main/fineweb-logo.png" alt="FineWeb: The finest collection of data the web has to offer"> </center>

15 trillion tokens of the finest data the 🌐 web has to offer

Table of Contents

• —🍷 FineWeb
• —What is it?
• —What is being released?
• —Changelog
• —How to download and use 🍷 FineWeb
• —Using 🏭 `datatrove`
• —Using `huggingface_hub`
• —Using `datasets`
• —Breakdown by dump/crawl
• —Dataset performance evaluation and ablations
• —Hyper-parameters for ablation models
• —Ablation evaluation benchmarks
• —Comparison with other datasets
• —Dataset card for 🍷 FineWeb
• —Dataset Summary
• —Dataset Structure
• —Data Instances
• —Data Fields
• —Data Splits
• —Dataset Creation
• —Curation Rationale
• —Source Data
• —Data processing steps
• —Annotations
• —Personal and Sensitive Information
• —Considerations for Using the Data
• —Social Impact of Dataset
• —Discussion of Biases
• —Other Known Limitations
• —Additional Information
• —Licensing Information
• —Future work
• —Citation Information

What is it?

The 🍷 FineWeb dataset consists of more than 18.5T tokens (originally 15T tokens) of cleaned and deduplicated english web data from CommonCrawl. The data processing pipeline is optimized for LLM performance and ran on the 🏭 `datatrove` library, our large scale data processing library.

🍷 FineWeb was originally meant to be a fully open replication of 🦅 RefinedWeb, with a release of the full dataset under the ODC-By 1.0 license. However, by carefully adding additional filtering steps, we managed to push the performance of 🍷 FineWeb well above that of the original 🦅 RefinedWeb, and models trained on our dataset also outperform models trained on other commonly used high quality web datasets (like C4, Dolma-v1.6, The Pile, SlimPajama, RedPajam2) on our aggregate group of benchmark tasks.

That said, we think there is still room for additional filtering and improvement and intend to continue exploring how to improve the dataset quality in coming versions of 🍷 FineWeb.

What is being released?

Along with the dataset, which includes all CommonCrawl dumps since 2013, we also share all the code needed to fully reproduce our processing setup using the 🏭 `datatrove` library here. To enable full replication of our results, we have also published the small ablation models we have trained using `nanotron` to validate the dataset and compare it with other reference datasets. You will find them here, with checkpoints every 1000 steps. We have also published our evaluation results here. Our evaluation setup is available here.

You will find details on the different processing decisions we took and some interesting explorations of deduplication methods on our blogpost.

Changelog

Previous versions remain available in the branch `version name`.

• —v1.4.0 (11-07-2025): Added 6 new snapshots: CC-MAIN-2025-05, CC-MAIN-2025-08, CC-MAIN-2025-13, CC-MAIN-2025-18, CC-MAIN-2025-21, and CC-MAIN-2025-26 (January to June 2025)
• —v1.3.0 (31-01-2025): Fixed an issue with some dumps where some documents hadn't been processed: CC-MAIN-2024-10, CC-MAIN-2024-18, CC-MAIN-2024-22, CC-MAIN-2024-26, CC-MAIN-2024-30, CC-MAIN-2024-33, CC-MAIN-2024-38, CC-MAIN-2024-42, CC-MAIN-2024-46 -- they now contain more data (~400B additional tokens). We also removed specific domains in response to a C&D notice.
• —v1.2.0 (03-01-2025): Added 8 new snapshots: CC-MAIN-2024-22, CC-MAIN-2024-26, CC-MAIN-2024-30, CC-MAIN-2024-33, CC-MAIN-2024-38, CC-MAIN-2024-42, CC-MAIN-2024-46, CC-MAIN-2024-51, covering May to December 2024.
• —v1.1.0 (31-05-2024): We reprocessed and reuploaded 11 dumps, CC-MAIN-2021-49 to CC-MAIN-2023-40, as we found a bug on their deduplication. We also added the most recent dump: CC-MAIN-2024-18, crawled over April 2024. Expect a small perf improvement
• —v1.0.0 (21-04-2024): Initial version

How to download and use 🍷 FineWeb

You can load the full dataset or a specific crawl/dump (see table below). Dumps have the format CC-MAIN-(year)-(week number).

(Smaller) sample versions

Along with config default (all the data), and the configs for each individual dump, you can also download the following configs:

• —sample-350BT: a subset randomly sampled from the whole dataset of around 350B gpt2 tokens (388GB)
• —sample-100BT: a subset randomly sampled from the whole dataset of around 100B gpt2 tokens (277.4GB)
• —sample-10BT: a subset randomly sampled from the whole dataset of around 10B gpt2 tokens (27.6GB)

sample-10B was sampled from sample-100B which in turn was sampled from sample-350BT.

Using 🏭 `datatrove`

from datatrove.pipeline.readers import ParquetReader

# limit determines how many documents will be streamed (remove for all)
# to fetch a specific dump: hf://datasets/HuggingFaceFW/fineweb/data/CC-MAIN-2024-10
# replace "data" with "sample/100BT" to use the 100BT sample
data_reader = ParquetReader("hf://datasets/HuggingFaceFW/fineweb/data", limit=1000) 
for document in data_reader():
    # do something with document
    print(document)

###############################    
# OR for a processing pipeline:
###############################

from datatrove.executor import LocalPipelineExecutor
from datatrove.pipeline.readers import ParquetReader
from datatrove.pipeline.filters import LambdaFilter
from datatrove.pipeline.writers import JsonlWriter

pipeline_exec = LocalPipelineExecutor(
    pipeline=[
        # replace "data/CC-MAIN-2024-10" with "sample/100BT" to use the 100BT sample
        ParquetReader("hf://datasets/HuggingFaceFW/fineweb/data/CC-MAIN-2024-10", limit=1000),
        LambdaFilter(lambda doc: "hugging" in doc.text),
        JsonlWriter("some-output-path")
    ],
    tasks=10
)
pipeline_exec.run()

Using huggingface_hub

from huggingface_hub import snapshot_download
folder = snapshot_download(
                "HuggingFaceFW/fineweb", 
                repo_type="dataset",
                local_dir="./fineweb/",
                # replace "data/CC-MAIN-2023-50/*" with "sample/100BT/*" to use the 100BT sample
                allow_patterns="data/CC-MAIN-2023-50/*")

For faster downloads, make sure to install pip install huggingface_hub[hf_transfer] and set the environment variable HF_HUB_ENABLE_HF_TRANSFER=1.

Using datasets

from datasets import load_dataset
# use name="sample-10BT" to use the 10BT sample
fw = load_dataset("HuggingFaceFW/fineweb", name="CC-MAIN-2024-10", split="train", streaming=True)

Breakdown by dump/crawl

Dataset performance evaluation and ablations

We conducted our dataset performance ablations and evaluations by training a series of 1.8B parameters models on 27 billion tokens. To compare 🍷 FineWeb with other datasets, we also trained one of these 1.8B models per target dataset, on 350 billion tokens sampled from it (or the entire dataset when its size was < 350 billion tokens).

Hyper-parameters for ablation models

The detailed configurations for training the 1.8B parameters ablation model can be found here (link will be added soon).

Ablation evaluation benchmarks

To conduct the ablations for each of our dataset filtering choices, we selected a set of benchmarks which we identified as “high-signal” benchmarks. These benchmarks were selected according to the following criteria:

• —small variance between runs trained on different samplings of the same dataset
• —performance increasing monotically during training (or close)
• —separation between runs on datasets of known quality (C4, The Pile, RedPajama) higher than the variance between runs with various modeling/data seeds

We used the following list of benchmark for our ablation runs:

• —commonsenseqa (acc/accnorm)
• —hellaswag (acc/acc_norm)
• —openbookqa (acc/acc_norm)
• —piqa (acc/acc_norm)
• —siqa (acc/acc_norm)
• —winogrande (acc/acc_norm)
• —arc (acc/acc_norm)
• —mmlu (acc/acc_norm)

To compare runs we consider an aggregate score, the average of the scores for these tasks.

The prompts for all these benchmarks are formatted in order to compute and compare the log-likelihood of the full answers for each multiple choice question. All the implementation details for the benchmarks are available in lighteval here.

Comparison with other datasets

We compared 🍷 FineWeb with the following datasets:

• —RefinedWeb
• —C4
• —Dolma v1.6 (the CommonCrawl part)
• —The Pile
• —SlimPajama
• —RedPajama2 (deduplicated)

You will find these models on this collection. We have uploaded checkpoints at every 1000 training steps. You will also find our full evaluation results here.

<center> <img src="https://huggingface.co/datasets/HuggingFaceFW/admin/resolve/main/fineweb-ablations.png" alt="ablations"> </center>

Note: The plot is smoothed by averaging 5k steps in a rolling window.

Dataset card for 🍷 FineWeb

Dataset Description

• —Homepage and Repository: https://huggingface.co/datasets/HuggingFaceFW/fineweb
• —Point of Contact: please create a discussion on the Community tab
• —License: Open Data Commons Attribution License (ODC-By) v1.0

Dataset Summary

This dataset was created by processing 96 CommonCrawl dumps comprising web data crawled from the summer of 2013 to April of 2024. 🍷 FineWeb includes a variety of domains and topics in English and is primarily intended to be used as a research artifact on public data in the context of pretraining dataset for large language models. The CommonCrawl data was carefully processed, filtered and deduplicated with the 🏭 `datatrove` library, resulting in the largest publicly available clean LLM pretraining dataset, counting around 15 trillion tokens (gpt2 tokenizer).

Dataset Structure

Data Instances

The following is an example sample from the dataset. It is part of the CC-MAIN-2021-43 and was crawled on 2021-10-15T21:20:12Z.

{
   "text": "This is basically a peanut flavoured cream thickened with egg yolks and then set into a ramekin on top of some jam. Tony, one of the Wedgwood chefs, suggested sprinkling on some toasted crushed peanuts at the end to create extra crunch, which I thought was a great idea. The result is excellent.",
   "id": "<urn:uuid:e5a3e79a-13d4-4147-a26e-167536fcac5d>",
   "dump": "CC-MAIN-2021-43",
   "url": "<http://allrecipes.co.uk/recipe/24758/peanut-butter-and-jam-creme-brulee.aspx?o_is=SimilarRecipes&o_ln=SimRecipes_Photo_7>",
   "date": "2021-10-15T21:20:12Z",
   "file_path": "s3://commoncrawl/crawl-data/CC-MAIN-2021-43/segments/1634323583083.92/warc/CC-MAIN-20211015192439-20211015222439-00600.warc.gz",
   "language": "en",
   "language_score": 0.948729,
   "token_count": 69
}

Data Fields

• —text (string): the main text content
• —id (string): original unique identifier for this sample from CommonCrawl
• —dump (string): the CommonCrawl dump this sample was a part of
• —url (string): url to the original page where text was present
• —date (string): crawl date (from CommonCrawl)
• —file_path (string): s3 path for the individual CommonCrawl warc file containing this sample
• —language (string): en for all the samples in this dataset
• —language_score (float): language prediction score (0.01.0) as reported by the fastText language classifier
• —token_count (int): number of tokens when applying the gpt2 tokenizer to this sample

Data Splits

The default subset includes the entire dataset. If you would like to only use the data from a particular CommonCrawl dump, you can use the dump name as a subset. You will find the full list of available dumps on the table above. From experiments we have run, not all dumps give the same performance. For relatively small trainings (<550 billion tokens) we recommend using the recent CC-MAIN-2023-50, CC-MAIN-2024-10 and CC-MAIN-2024-18.

Dataset Creation

Curation Rationale

While multiple open-weights models have regularly been released in recent months, these releases often do not include the model's training data. With 🍷 FineWeb we aim to provide the open source community with a very large clean pretraining dataset that can be used to push the envelope on truly open source models (open source models where data is also released).

Source Data

The source data consists of webpages crawled by the CommonCrawl foundation over the 2013-2024 time period.

We then extracted the main page text from the html of each webpage, carefully filtered each sample and deduplicated each individual CommonCrawl dump/crawl.

While we originally intended to deduplicate the dataset as a whole, our ablations showed that training on a sampling of individually deduplicated dumps/crawls outperformed training on a sampling of all the dumps/crawls deduplicated together. You will find more details on our blogpost.

Data processing steps

We used the 🏭 datatrove library to process the data. You can find a working script that launches the entire processing pipeline here.

The data processing pipeline consists of:

1. 1.Url Filtering, removing documents originating from Malicious and NSFW websites, using both block-list as well as subwords detection
2. 2.Trafilatura text extraction on the raw HTML from CommonCrawl’s warc files
3. 3.FastText LanguageFilter, removing any document with en language score lower than 0.65
4. 4.Quality filtering
5. 5.Gopher Repetition / Quality
6. 6.C4 Quality filters except terminal_punct rule
7. 7.FineWeb custom filters, consisting of heuristics for removing list-like documents, documents with repeated lines and documents with likely wrong line formatting.
8. 8.MinHash deduplication with each crawl deduplicated individually (5-grams, 14x8 hash functions)
9. 9.PII Formatting to anonymize email and public IP addresses

Annotations

We augment the original samples with the language, language_score and token_count annotations. The language related annotations are automatically generated by our language filter. token_count is generated by applying the gpt2 tokenizer to the text column.

Personal and Sensitive Information

We anonymize email addresses and public IP addresses.

For emails, we apply a regex pattern and replace any occurrence of an email address with either email@example.com or firstname.lastname@example.org. For IP addresses, we also employ a regex pattern and then further filter to only anonymize IP addresses allocated for public networks. Matched IP addresses are then replaced with one of the following randomly generated IP addresses, which at the time of dataset creation were not responding to ping requests: 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, and 18.104.22.168. We decided against applying regex patterns for phone numbers due to the high false positive rate.

Despite our efforts, given that 🍷 FineWeb is sourced from the internet at large, it is very likely that some personable identifiable information (PII) will be present. If you find your own PII in 🍷 FineWeb and would like it removed, please fill out our PII removal form.

Considerations for Using the Data

Social Impact of Dataset

With the release of this dataset we aim to make model training more accessible to the machine learning community at large.

While multiple open-weights models with strong performance have been publicly released in the past, more often than not these releases are not accompanied by the corresponding training dataset. This is unfortunate as the dataset specificities and characteristics have been demonstrated to have a very large impact and role in the performances of the models. As the creation of a high quality training dataset is a fundamental requirement to training an LLM capable of excelling at downstream tasks, with 🍷 FineWeb we (a) not only make the dataset creation process more transparent, by sharing our entire processing setup including the codebase used, we also (b) help alleviate the costs of dataset curation, both in time and in compute, for model creators by publicly releasing our dataset with the community.

Discussion of Biases

Efforts were made to minimize the amount of NSFW and toxic content present in the dataset by employing filtering on the URL level. However, there are still a significant number of documents present in the final dataset that could be considered toxic or contain harmful content. As 🍷 FineWeb was sourced from the web as a whole, any harmful biases typically present in it may be reproduced on our dataset.

We deliberately avoided using machine learning filtering methods that define text quality based on the similarity to a “gold” source such as wikipedia or toxicity classifiers as these methods have been known to disproportionately remove content in specific dialects and overclassify as toxic text related to specific social identities, respectively.

Other Known Limitations

As a consequence of some of the filtering steps applied, it is likely that code content is not prevalent in our dataset. If you are training a model that should also perform code tasks, we recommend you use 🍷 FineWeb with a code dataset, such as The Stack v2. You should also probably consider complementing 🍷 FineWeb with specialized curated sources (such as Wikipedia, for example) as they will likely have better formatting than the wikipedia content included in 🍷 FineWeb (we did not tailor the processing to individual websites).

Additional Information

Licensing Information

The dataset is released under the Open Data Commons Attribution License (ODC-By) v1.0 license. The use of this dataset is also subject to CommonCrawl's Terms of Use.

Future work

We plan to not only continue but also expand our efforts to create open-source high quality training datasets and to improve 🍷 FineWeb itself in future iterations.

Citation Information

Paper on arXiv

@inproceedings{
  penedo2024the,
  title={The FineWeb Datasets: Decanting the Web for the Finest Text Data at Scale},
  author={Guilherme Penedo and Hynek Kydl{\'\i}{\v{c}}ek and Loubna Ben allal and Anton Lozhkov and Margaret Mitchell and Colin Raffel and Leandro Von Werra and Thomas Wolf},
  booktitle={The Thirty-eight Conference on Neural Information Processing Systems Datasets and Benchmarks Track},
  year={2024},
  url={https://openreview.net/forum?id=n6SCkn2QaG}
}