--- title: Amazon ECR now supports image layers up to 200 GB description: Amazon ECR has raised the maximum image layer size to 200 GB for images pushed via Docker push, up from the previous limit. This removes the need to split... canonical: https://daily.dev/posts/amazon-ecr-now-supports-image-layers-up-to-200-gb-eri1dqxna twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Amazon ECR now supports image layers up to 200 GB | daily.dev og:description: Amazon ECR has raised the maximum image layer size to 200 GB for images pushed via Docker push, up from the previous limit. This removes the need to split... og:url: https://daily.dev/posts/amazon-ecr-now-supports-image-layers-up-to-200-gb-eri1dqxna og:image: https://api.daily.dev/og/posts/erI1DqxnA.png og:image:alt: Amazon ECR now supports image layers up to 200 GB 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. # Amazon ECR now supports image layers up to 200 GB **[AWS](https://daily.dev/sources/aws)** · 1 min read · 0 upvotes · 1 comments ## Summary Amazon ECR has raised the maximum image layer size to 200 GB for images pushed via Docker push, up from the previous limit. This removes the need to split large assets across multiple layers or use external storage, making it easier to embed large language models, genomics datasets, or large binary dependencies directly in container images. The 50 GB limit still applies when using the AWS SDK or CLI (UploadLayerPart API). The feature is available in all ECR-supported AWS regions except Middle East (Bahrain) and Middle East (UAE). ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@trevorsuna** · 0 upvotes > This removes a hard blocker for very large model artifacts, but a 200 GB layer can still make pulls and rollbacks painful. Keeping frequently changed files in smaller layers should preserve cache reuse and reduce the operational cost of each update. ## Similar posts on daily.dev - [Amazon ECR introduces archive storage class for rarely accessed container images](https://daily.dev/posts/amazon-ecr-introduces-archive-storage-class-for-rarely-accessed-container-images-rfgxzdqgg) · AWS · 0 upvotes · 0 comments - [AWS Introduces Remote Build Cache in ECR to Accelerate Docker Image Builds](https://daily.dev/posts/aws-introduces-remote-build-cache-in-ecr-to-accelerate-docker-image-builds-dc8dqcb5c) · InfoQ · 0 upvotes · 0 comments - [Amazon ECR now supports pull through cache for Chainguard](https://daily.dev/posts/amazon-ecr-now-supports-pull-through-cache-for-chainguard-ci33mvca3) · AWS · 1 upvotes · 0 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#llm](https://daily.dev/tags/llm), [#containers](https://daily.dev/tags/containers) [View this post on daily.dev](https://daily.dev/posts/amazon-ecr-now-supports-image-layers-up-to-200-gb-eri1dqxna) ```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":"Amazon ECR now supports image layers up to 200 GB","url":"https://daily.dev/posts/amazon-ecr-now-supports-image-layers-up-to-200-gb-eri1dqxna","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/amazon-ecr-now-supports-image-layers-up-to-200-gb-eri1dqxna"},"datePublished":"2026-08-03T16:04:23.465Z","dateModified":"2026-08-24T07:02:31.452Z","description":"Amazon ECR has raised the maximum image layer size to 200 GB for images pushed via Docker push, up from the previous limit. This removes the need to split...","image":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","thumbnailUrl":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","isAccessibleForFree":true,"articleSection":"AWS","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":"AWS","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/aws","url":"https://daily.dev/sources/aws"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/amazon-ecr-now-supports-image-layers-up-to-200-gb-eri1dqxna","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"aws,llm,containers","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"AWS","item":"https://daily.dev/sources/aws"},{"@type":"ListItem","position":3,"name":"Amazon ECR now supports image layers up to 200 GB"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/amazon-ecr-now-supports-image-layers-up-to-200-gb-eri1dqxna","comment":[{"@type":"Comment","text":"This removes a hard blocker for very large model artifacts, but a 200 GB layer can still make pulls and rollbacks painful. Keeping frequently changed files in smaller layers should preserve cache reuse and reduce the operational cost of each update.","datePublished":"2026-08-04T05:13:52.634Z","url":"https://daily.dev/posts/erI1DqxnA#c-WxWROz7yZ","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"}}]} ```