Paste a Dockerfile and estimate layer sizes with optimization tips for smaller image builds.
A Dockerfile can indicate where image weight may come from, but it cannot disclose the finished byte count. This analyzer reads pasted Dockerfile instructions, assigns size estimates to the layers they imply, and presents optimization tips for size-relevant choices. Its most important boundary is the missing build data: base image contents, files copied from the build context, downloaded packages, and generated artifacts are not contained in the Dockerfile. The result is planning guidance, not a substitute for building and inspecting the image.
The input is Dockerfile source, so the estimate can reason from FROM and filesystem-changing instructions such as RUN, COPY, and ADD. It has no byte-level evidence for referenced build-context files, remote downloads, package selections, or generated output. Any size assigned to those steps is therefore an estimate based on the text, not a measurement of their resulting layer archives.
Optimization advice should be interpreted with Docker's immutable layer model in mind. Removing a file in a later layer does not remove its bytes from an earlier layer. Keeping temporary downloads and their deletion in one RUN step, or copying only runtime artifacts from a build stage, can reduce final image content when those techniques fit the Dockerfile.
No. Exact size depends on the resolved base image, build context, fetched content, target platform, and actual command output. Build the image for its target platform, then inspect the resulting image and layer history. Even then, distinguish image content from registry transfer size because registry blobs can be compressed and already-present layers may be reused.
No. In an ordinary layered image, a later deletion hides the path from the resulting filesystem view but leaves its earlier bytes in the image. Creating and deleting temporary files within the same RUN instruction can keep them out of that step's final filesystem change. Multi-stage builds can also exclude build-only material from the final image.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.