--- title: Vercel Container Registry repositories can now be made... description: Vercel Container Registry now supports making repositories public, allowing any Vercel team to pull and use images with read-only access. Previously, sharing... canonical: https://daily.dev/posts/vercel-container-registry-repositories-can-now-be-made-public-ughrgn7zv twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Vercel Container Registry repositories can now be made public | daily.dev og:description: Vercel Container Registry now supports making repositories public, allowing any Vercel team to pull and use images with read-only access. Previously, sharing... og:url: https://daily.dev/posts/vercel-container-registry-repositories-can-now-be-made-public-ughrgn7zv og:image: https://api.daily.dev/og/posts/UGHRgn7Zv.png og:image:alt: Vercel Container Registry repositories can now be made public og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Vercel Container Registry repositories can now be made public **[Vercel](https://daily.dev/sources/vercel)** · 1 min read · 1 upvotes · 2 comments ## Summary Vercel Container Registry now supports making repositories public, allowing any Vercel team to pull and use images with read-only access. Previously, sharing was limited to up to 100 named teams. Public repositories can be configured via the project dashboard (Images → repository → Settings → Public Access), the Vercel CLI using `vercel vcr config --public true/false`, or the REST API. Repositories remain private by default, and public access is strictly read-only — no push, delete, or modification is permitted. Public images integrate with Vercel Sandbox via a team-scoped image reference in `Sandbox.create()` ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I make a Vercel Container Registry repository public? Set the repository's visibility to public from the project dashboard under Images → repository → Settings → Public Access, confirming by typing the repository name, or run vercel vcr config --public true from the CLI. This grants read-only pull access to every Vercel team rather than a limited, named set of teams. Repositories remain private by default, and the same toggle also works through the REST API. _daily.dev keeps developers current on registry and deployment changes like this one from Vercel._ ### How many teams could access a shared Vercel Container Registry repository before public visibility was added? Sharing supported granting read access to up to 100 named teams before public visibility existed. Making a repository public removes that cap, opening read-only pull access to every Vercel team instead of a fixed list, while push, delete, and other write operations remain restricted regardless of visibility setting. _Teams evaluating image-sharing limits can track platform updates like this via daily.dev._ ### How do I reference a public Vercel Container Registry image in Vercel Sandbox? Pass a team-scoped image reference to Sandbox.create(), such as image: 'their-team/their-project/their-repository:latest'. Public images behave the same way shared images already did in Vercel Sandbox, so no additional configuration is needed beyond making the source repository public or already-shared. _daily.dev helps developers building on Vercel Sandbox stay on top of image-sharing changes like this._ ## Community discussion Top comments from developers on daily.dev. **@trevorsuna** · 0 upvotes > Public, read-only repositories are a useful middle ground for demo images and shared base layers. Keeping private as the default matters; I’d also want clear pull metrics and a simple way to rotate or deprecate tags, because public access makes stale images much easier to depend on. **@fahimahammed** · 0 upvotes > This is a great addition. Making Vercel Container Registry repositories public while keeping access strictly read-only makes sharing and reusing container images much simpler, especially for teams using Vercel Sandbox. 🚀 ## Similar posts on daily.dev - [Share Vercel Container Registry repositories across teams](https://daily.dev/posts/share-vercel-container-registry-repositories-across-teams-kgcvxanbn) · Vercel · 1 upvotes · 1 comments - [Push images to Vercel Container Registry from GitHub Actions](https://daily.dev/posts/push-images-to-vercel-container-registry-from-github-actions-at2yrkyub) · Vercel · 2 upvotes · 1 comments - [Introducing Multiple Registry Support on DigitalOcean Container Registry](https://daily.dev/posts/introducing-multiple-registry-support-on-digitalocean-container-registry-yo8dtedtf) · DigitalOcean · 6 upvotes · 0 comments --- Tags: [#docker](https://daily.dev/tags/docker), [#containers](https://daily.dev/tags/containers), [#vercel](https://daily.dev/tags/vercel) [View this post on daily.dev](https://daily.dev/posts/vercel-container-registry-repositories-can-now-be-made-public-ughrgn7zv) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Vercel Container Registry repositories can now be made public","url":"https://daily.dev/posts/vercel-container-registry-repositories-can-now-be-made-public-ughrgn7zv","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/vercel-container-registry-repositories-can-now-be-made-public-ughrgn7zv"},"datePublished":"2026-08-07T18:01:19.086Z","dateModified":"2026-09-14T09:31:30.757Z","description":"Vercel Container Registry now supports making repositories public, allowing any Vercel team to pull and use images with read-only access. Previously, sharing...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/60f0c4387f13af6d9f2336417495b9ff?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/60f0c4387f13af6d9f2336417495b9ff?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Vercel","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Vercel","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/04cca7235cf84db092f24b7ba427b3e1","url":"https://daily.dev/sources/vercel"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/vercel-container-registry-repositories-can-now-be-made-public-ughrgn7zv","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"docker,containers,vercel","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Vercel","item":"https://daily.dev/sources/vercel"},{"@type":"ListItem","position":3,"name":"Vercel Container Registry repositories can now be made public"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/vercel-container-registry-repositories-can-now-be-made-public-ughrgn7zv","comment":[{"@type":"Comment","text":"Public, read-only repositories are a useful middle ground for demo images and shared base layers. Keeping private as the default matters; I’d also want clear pull metrics and a simple way to rotate or deprecate tags, because public access makes stale images much easier to depend on.","datePublished":"2026-08-09T04:21:50.832Z","url":"https://daily.dev/posts/UGHRgn7Zv#c-ARtxMSqwe","author":{"@type":"Person","name":"Trevor Suna","url":"https://daily.dev/trevorsuna","image":"https://media.daily.dev/image/upload/s--dZ7gXxpp--/f_auto/v1784081551/avatars/avatar_EMoP47rpuw8DNjhp6R1b6?_a=BAMAMicg0"}},{"@type":"Comment","text":"This is a great addition. Making Vercel Container Registry repositories public while keeping access strictly read-only makes sharing and reusing container images much simpler, especially for teams using Vercel Sandbox. 🚀","datePublished":"2026-08-09T05:59:01.981Z","url":"https://daily.dev/posts/UGHRgn7Zv#c-P037Gcxlo","author":{"@type":"Person","name":"Fahim Ahammed Firoz","url":"https://daily.dev/fahimahammed","image":"https://lh3.googleusercontent.com/a/ACg8ocLPDnjeV4QsaVwi1lXMBgMAKbog9I4fgMTTJnHRKE-Uc1NmSJY0=s96-c"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/vercel-container-registry-repositories-can-now-be-made-public-ughrgn7zv#faq","mainEntity":[{"@type":"Question","name":"How do I make a Vercel Container Registry repository public?","acceptedAnswer":{"@type":"Answer","text":"Set the repository's visibility to public from the project dashboard under Images → repository → Settings → Public Access, confirming by typing the repository name, or run vercel vcr config --public true from the CLI. This grants read-only pull access to every Vercel team rather than a limited, named set of teams. Repositories remain private by default, and the same toggle also works through the REST API. daily.dev keeps developers current on registry and deployment changes like this one from Vercel."}},{"@type":"Question","name":"How many teams could access a shared Vercel Container Registry repository before public visibility was added?","acceptedAnswer":{"@type":"Answer","text":"Sharing supported granting read access to up to 100 named teams before public visibility existed. Making a repository public removes that cap, opening read-only pull access to every Vercel team instead of a fixed list, while push, delete, and other write operations remain restricted regardless of visibility setting. Teams evaluating image-sharing limits can track platform updates like this via daily.dev."}},{"@type":"Question","name":"How do I reference a public Vercel Container Registry image in Vercel Sandbox?","acceptedAnswer":{"@type":"Answer","text":"Pass a team-scoped image reference to Sandbox.create(), such as image: 'their-team/their-project/their-repository:latest'. Public images behave the same way shared images already did in Vercel Sandbox, so no additional configuration is needed beyond making the source repository public or already-shared. daily.dev helps developers building on Vercel Sandbox stay on top of image-sharing changes like this."}}]} ```