Maven Central Publishing Limits - Documentation

Skip to content

Initializing search

Requirements

Publishing via the Central Portal

Generating a Portal Token for Publishing

Maven

Publisher API

Upload

Gradle

OSSRH Staging API

Snapshots

Publisher Insights

Usage Center

Producer Terms

CONSUME

FAQ

CENTRAL SEARCH

SUPPORT

WHO IS SONATYPE?

CHANGELOG

STATUS & NEWS

Maven Central Publishing Limits⚓︎

What's Changing?⚓︎

Maven Central is introducing publishing usage visibility and limits for high-volume publishing activity. These changes are focused on publishing patterns that operate at commercial or infrastructure scale: unusually large artifacts, high file counts, very high release frequency, or repeated high-volume publishing across an organization's namespaces.

Maven Central is critical infrastructure for the Java ecosystem: a shared place where open source projects publish release-ready components and millions of developers reliably consume them. That role is not changing. Maven Central remains free for ordinary community open source publishing within the free limits.

But publishing demand is no longer evenly distributed. Maven Central now supports both ordinary open source releases and high-scale publishing patterns from commercial platforms, automated pipelines, SDKs, generated clients, agents, integrations, and other software delivery systems. Those patterns create a different kind of demand on shared infrastructure.

Publishing size, file count, and release frequency are useful signals for distinguishing these use cases. They are not perfect measures of intent, and they are not meant to punish legitimate open source activity. They help distinguish community-scale publishing from commercial-scale or infrastructure-driven use, so Maven Central can remain free for most publishers while giving higher-volume organizations a clear paid path through Maven Central Publisher Pro.

Publishing usage is now available in Maven Central through the Usage Center. Hard enforcement is scheduled to begin on August 11, 2026. Starting then, publishers that exceed the free limits will have publishing activity capped until usage resets, usage is reduced, an exemption is approved, or a paid option is in place.

Why is Sonatype Making This Change?⚓︎

This change is part of a broader industry effort to keep public package infrastructure reliable, secure, and open for the long term. Across ecosystems, registries are facing the same pressures: rising automation, CI/CD, security scanning, machine-driven software supply chains, and commercial platforms using public registries as production infrastructure.

For more context on this broader effort, see:

Open Infrastructure Is Not Free: A Joint Statement on Sustainable Stewardship

Open Infrastructure Is Not Free, Part II: The Hidden Cost of Running Package Registries

Open Is Not Costless: Reclaiming Sustainable Infrastructure

Maven Central and the Tragedy of the Commons

Beyond IPs: Addressing Organizational Overconsumption in Maven Central

Open Publishing, Commercial Scale

Maven Central is part of that same shift. It serves millions of developers and over 1.5 trillion downloads annually, but the operational demand is not distributed evenly. A relatively small group of very high-volume users and publishers creates a disproportionate share of the load through commercial-scale consumption and publishing patterns.

On the publishing side, the data shows the same concentration:

In the past 90 days, 10% of namespaces accounted for:<br>more than 88% of all files published to Maven Central

more than 90% of total storage consumed by new releases

over 70% of all new release events

What Stays the Same?⚓︎

Maven Central's core purpose is not changing. It remains a public distribution platform for release-ready community open source software in the Java ecosystem.

For most publishers:

Existing publishing workflows remain unchanged.

Public artifacts already published to Maven Central remain available for download.

Community open source projects should generally be unaffected by these limits. Projects with unusual publishing patterns can request an exemption for review.

Developers and consumers can continue to rely on Maven Central as the default source for public Java components.

The new limits are focused on high-volume publishing patterns that operate at commercial or infrastructure scale. They are not intended to disrupt ordinary community open source publishing.

What Are the Maven Central Publishing Limits?⚓︎

Maven Central tracks three monthly publishing metrics per organization: file count , release size , and release count . Limits are evaluated per organization and may include one or more namespaces.

The current thresholds — and where your organization stands relative to them — are always visible in the Usage Center. Limits may be adjusted after the soft-limit phase as we better understand real-world publishing patterns.

The charts below show where the...