←  Back to Blog
May 28, 2025

May 2025 Crawl Archive Now Available

We are pleased to announce that the crawl archive for May 2025 is now available. The data was crawled between May 11th and May 25th, and contains 2.47 billion web pages, or 429 TiB of uncompressed content.

The crawl archive for May 2025 is now available.

The data was crawled between May 11th and May 25th, and contains 2.47 billion web pages (or 429 TiB of uncompressed content). Page captures are from 46.9 million hosts or 38.2 million registered domains and include 654 million new URLs, not visited in any of our prior crawls.

File List #Files Total Size
Compressed (TiB)
Segments segment.paths.gz 100
WARC warc.paths.gz 100000 89.29
WAT wat.paths.gz 100000 16.78
WET wet.paths.gz 100000 6.67
Robots.txt robotstxt.paths.gz 100000 0.15
Non-200 responses non200responses.paths.gz 100000 3.09
URL index cc-index.paths.gz 302 0.19
Columnar URL index cc-index-table.paths.gz 900 0.22

Archive Location & Download

The May 2025 crawl archive is located in the commoncrawl bucket at crawl-data/CC-MAIN-2025-21/.

To assist with exploring and using the dataset, we provide gzip compressed files which list all segments, WARC, WAT and WET files.

By simply adding either s3://commoncrawl/ or https://data.commoncrawl.org/ to each line, you end up with the S3 and HTTP paths respectively, please see Get Started for detailed instructions.

This release was authored by:
Pedro is a Principal Research Scientist at the Common Crawl Foundation.
Pedro Ortiz Suarez
Pedro is a Principal Research Scientist at the Common Crawl Foundation.
Thom is Principal Engineer at the Common Crawl Foundation.
Thom Vaughan
Thom is Principal Engineer at the Common Crawl Foundation.

Erratum: 

WARC Content-Type header in revisit records

Originally reported by: 
Sebastian Nagel
More details
Common Crawl's WARC revisit records use Content-Type: message/http (following the WARC 1.1 spec's example), but per iipc/warc-specifications#55 it should be application/http;msgtype=response for consistency with other HTTP response records.

Erratum: 

Content is truncated

Originally reported by: 
More details
Some archived content is truncated due to fetch size limits imposed during crawling. This is necessary to handle infinite or exceptionally large data streams (e.g., radio streams). Prior to March 2025 (CC-MAIN-2025-13), the truncation threshold was 1 MiB. From the March 2025 crawl onwards, this limit has been increased to 5 MiB.