Vercel Adds Public Access to Container Registry Repositories.

Vercel is opening its Container Registry beyond private team distribution. Repositories can now be made public, allowing anyone with a Vercel account to pull and use their container images while keeping write access locked down.

The change, announced in Vercel’s changelog on August 7, 2026, gives developers a more direct way to distribute reusable images through the company’s own infrastructure. Until now, every repository in Vercel Container Registry was private.

Public repositories are available to every Vercel team rather than a list of individually approved teams. That distinction matters because this is not unrestricted, anonymous access from anywhere on the internet. A person still needs a Vercel account to pull and use the images.

The access is also strictly read-only. Other teams can:

• Pull images from the repository
• Use those images in their own work
• Access the repository without being individually added

They cannot push new images, delete existing images, or otherwise modify the repository. The owner therefore retains control over what is published while gaining a broader distribution channel.

Previously, owners could grant read access to as many as 100 named teams. That model remains useful for private partnerships, clients, or internal organizations, but it creates administrative work when an image is intended for a larger audience. Public visibility removes the need to maintain that access list.

For small development teams, the update could simplify the release of common runtime environments, starter images, open-source components, and reference implementations. An agency could publish a standard image for client teams, for example, without inviting every client individually. A tool builder could distribute a supported image through Vercel while preventing downstream users from changing the source repository.

Vercel has placed the visibility control inside the project dashboard. Repository owners can navigate to Images, select the repository, open Settings, and then choose Public Access.

Making that change requires typing the repository name as confirmation. This extra step is intended to reduce accidental exposure, particularly where a repository may contain images that were originally created under the assumption that access was limited.

Visibility can also be configured through the Vercel CLI, according to the announcement. That option should make the setting easier to incorporate into scripted setup processes or infrastructure workflows, although Vercel’s short changelog post does not provide the command syntax.

Repositories remain private by default. Existing repositories will not automatically become visible to other teams, and creating a new repository does not expose it unless an owner deliberately changes the setting.

That default is important because container images can include application code, installed packages, configuration defaults, and other implementation details. Before enabling public access, teams should review image contents and build processes just as they would before publishing any other software artifact.

The release is narrower than a general-purpose public container registry, since pulls remain tied to Vercel accounts. Still, it closes a practical gap for developers who build and deploy on Vercel but previously needed a separate distribution mechanism when an image had to reach more than 100 teams. It also preserves a clear boundary between consumption and maintenance: the wider Vercel community can use a public image, but only authorized maintainers can alter its repository.

What are public Vercel Container Registry repositories?

They are container image repositories that every Vercel team can access on a read-only basis. Anyone with a Vercel account can pull and use their images, but cannot push, delete, or modify repository contents.

Are existing Vercel Container Registry repositories automatically public?

No. Repositories remain private by default, including existing repositories. An owner must deliberately enable Public Access from the repository settings or change visibility through the Vercel CLI.

How is public access different from the previous sharing model?

Previously, a repository owner could grant read access to up to 100 named teams. Public access extends read-only availability to every Vercel team without requiring the owner to manage an individual access list.