TechnSols
Advertisement

Docker Image Layer Explorer

Explore Docker image layers online for free. Upload a docker save tar and see layers, sizes, and history, with no install and no sign-up.

Be the first to rate this tool

Plain .tar, gzipped .tar.gz, or a .zip holding a docker save tar. Files over 100 MB are refused. Nothing is uploaded.

Upload a docker save .tar file to list its layers.

What Is Docker Image Layer Explorer?

Docker Image Layer Explorer is a free online tool by TechnSols that opens a docker save tar file and lists the layers inside, with their sizes, commands, and file counts. You upload the .tar file, and the tool reads the manifest and every layer in your browser.

Advertisement

A Docker image is a stack of layers, and each layer is a tar file holding the files one build step added. The docker save docs explain how docker save packs those layers, the manifest, and the config into one tar file, and this explorer unpacks that format for you, layer by layer, without Docker installed.

The tool parses the tar headers itself, reads manifest.json for the layer order and the image tags, and reads the config JSON for the build history. If the image was built from a Dockerfile, the Dockerfile Generator tool writes the Dockerfile that made it.

People use it to find why an image is large, to check what a layer added, and to confirm an image holds the files it should. It suits a bloated image, a handover where nobody remembers the build, or a review before a registry push. The report it writes is JSON, so you can keep it with the build.

How To Use Docker Image Layer Explorer?

Here is how to explore Docker image layers online in three quick steps. Using Docker Image Layer Explorer is simple. There is no software to install and no account to make. Save the image, upload the tar, and read the layers. If the stack runs the image, the Docker Compose Builder tool builds that stack.

Step 1: Save The Image As A Tar

On the machine that holds the image, run docker save -o image.tar my-image:tag, replacing the name and tag with your own. The command writes one tar file holding the manifest, the config, and one tar file per layer. Do not use docker export: it writes a filesystem with no layer history, and this tool needs the history to list the layers.

Step 2: Upload The Tar File

Press Choose File and pick the .tar file, or drag it onto the drop zone. The file guard checks the extension and the magic bytes, and files over 100 MB are refused, because the whole tar is read in your browser. A gzipped .tar.gz or a .zip holding a docker save tar works too, and the tool detects the format from the file itself.

Step 3: Read The Layers And Download

Read the layer list from the base up: each layer shows its size, its digest, the command that created it, and its file count. The largest layer is marked, and the total size sits at the bottom. Download the JSON report when you need it later. If the tar itself will not open, the Zip Extractor tool opens archives the same way.

The whole job takes a few minutes. A file built from a form is ready to use, and the steps above are the same every time.

Why Docker Image Layer Explorer?

An image that grew to a gigabyte did not grow in one step: one layer added a package cache, another copied a build folder, and a later layer deleted the files without shrinking the image, because deleted files still ship in their layer. The explorer shows which layer holds the weight, so the fix goes to the right Dockerfile line instead of a guess. If the image runs in a cluster, the Kubernetes Manifest Validator tool checks the manifests that deploy it.

The format it reads is the open image format Docker documents. The dive project is the local tool that explores images the same way, layer by layer, and this explorer brings that idea to the browser for a saved tar. The numbers come from the tar headers and the manifest, not from estimates.

The Biggest Layer Is Marked

Most of an image weight sits in one or two layers, and the rest is noise. The explorer marks the largest layer, so the first look lands on the problem: a copied build folder, an unneeded package, or a cache that was never cleaned. Slimming starts there, not with a guess.

History Explains Each Layer

Every layer carries the command that created it, such as RUN apt-get install or COPY . /app, taken from the image config history. Reading the commands in order tells the story of the build, and a command that looks wrong is usually the layer that is too large.

No Docker Needed

Exploring an image normally needs Docker installed and the image loaded, which is slow on a machine that only reviews images. This tool reads the saved tar directly, so a reviewer, a student, or a teammate without Docker can still open the image. If the pipeline that built the image needs a map, the Pipeline Visualizer tool draws it.

What Can You Do With Docker Image Layer Explorer?

An image explorer fits any image that is too large or too mysterious. These are the jobs this explorer handles best.

Find Why An Image Is Large

Upload the saved tar, read the layer list, and look at the marked largest layer and its command. A COPY of a build folder or an apt cache left in place is the usual cause. Fix the Dockerfile line, rebuild, save again, and compare the totals.

Check What A Layer Added

Read the file count and the largest files of a layer to confirm it holds what it should. A layer that should hold only the app code but shows thousands of files has a copying problem, usually a missing .dockerignore. The Image to PDF tool turns a screenshot of the list into a PDF to share.

Confirm An Image Before A Push

Save the image, explore it, and check the tags, the layer count, and the total size before the push. An image with an unexpected layer or a secret file in the history is caught here, not after it is public in the registry.

Advertisement

Quality And Settings

The tool reads the outer tar with its own 512-byte header parser, finds manifest.json, and reads the layer order, the RepoTags, and the config file name. Each layer tar is parsed the same way to count its files and find its largest files, and the config JSON gives the history commands. The total is the sum of the layer sizes plus the config and manifest. If the tar itself is gzipped, it is decompressed in the browser first. If the manifest is JSON, the JSON Validator tool checks that form on its own.

  • Reads plain .tar, gzipped .tar.gz, and .zip files holding a docker save tar.
  • Parses tar headers directly, with no server and no Docker install.
  • Lists every layer with size, digest, command, and file count.
  • Marks the largest layer and totals the whole image.
  • Downloads the full layer report as JSON.

There are no other settings to learn, because the tar holds everything. Save the image, upload the tar, and read the layers. If a layer tar is corrupt, the tool reports the layer it failed on and lists the rest, so one bad layer does not hide the whole image.

How Docker Image Layer Explorer Works

The explorer reads the uploaded file into memory, detects the format from its magic bytes, and decompresses it when it is gzipped. It then walks the tar entries in 512-byte blocks, reading each header name, size, and type, and collects the manifest.json and config JSON. The manifest gives the layer order, and each layer tar is walked the same way to count files and find the largest ones. If the archive is a plain tar, the Tar File Extractor tool lists every file in it the same way.

Two limits are worth knowing. The tool lists layers and counts files, and it does not unpack the merged filesystem, so it cannot show the final file tree the way a local tool can. It also reads the whole tar in your browser, so a very large image needs a machine with enough memory, and files over 100 MB are refused. For a full filesystem view, use dive on your own machine.

Privacy

Everything you upload stays in your browser. The tar file is read on your own computer, and nothing you upload is sent to a server, stored, or shared with anyone. Closing the tab clears the file, so the image contents never leave your device.

Because no account is needed, there is no name, email, or history tied to what you explore. Closing the tab ends the session, and the browser clears the input from memory. That is the same protection on every tool here: your work stays yours, and nothing about it is kept, shared, or sold.

Tips

A few habits make Docker Image Layer Explorer work smoother, whether this is your first file or your fiftieth.

  • Save with docker save, never docker export, or the layers are lost.
  • Combine RUN commands and clean caches in the same layer that made them.
  • Add a .dockerignore before the first build, not after the image is large.
  • Pin base image tags, so a rebuild does not pull a bigger base.
  • Compare the total before and after a slimming change, and keep the report.

When the image is slim, save it again and explore the new tar to confirm the total dropped. If a gzipped layer needs opening on its own, the Gzip Decompressor tool opens it.

More Tools For The Same Job

These tools handle the same kinds of jobs: building, opening, and checking container images and archives.

FAQ

Common questions about exploring Docker image layers, answered plainly.

Is Docker Image Layer Explorer by TechnSols Free?

Yes, Docker Image Layer Explorer by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can explore as many saved images as you like, and everything you upload stays in your browser, so nothing is uploaded or stored anywhere.

How Do I Save An Image To Explore?

Run docker save -o image.tar my-image:tag on the machine that holds the image, then upload the .tar file here. The file holds the manifest, the config, and one tar file per layer. A container export from docker export is different: it holds a filesystem with no layer history, so this tool cannot explore it.

Which Files Can I Upload?

You can upload a plain .tar file from docker save, a gzipped .tar.gz, or a .zip that holds a docker save tar. The file guard checks the extension and the magic bytes, and files over 100 MB are refused. Very large images take a while to read, because every layer is parsed in your browser.

What Does Each Layer Show?

Each layer shows its size, its digest, the command that created it from the image history, and how many files it holds. The total shows the sum of the layers, and the largest layer is marked, so the place to start slimming the image is obvious. The report can be downloaded as JSON.

Can It Show Which Files A Layer Added?

Yes, for layers it can parse, the tool counts the files each layer tar holds and lists the largest files it finds. It does not unpack the whole filesystem, so it cannot show the merged view of all layers at once. For a full filesystem view, use a local tool such as dive on your own machine.

Save the image, upload the tar, and read the layers. An image you can see inside is an image you can slim, and that is the whole point of exploring it.

Follow TechnSols on Google
Add TechnSols as a preferred source to see more of our tools in Google Search.
Add to Preferred Sources
Advertisement