Open CPIO files on Mac
To open a CPIO archive on Mac, use the Mac's libarchive-based tar to list and extract it, or browse it in Kernir. CPIO can hold files, folders and filesystem metadata. Kernir reads CPIO but does not create or save CPIO archives.
Inspect the stored paths
CPIO archives may come from an older backup, a software package or a Unix workflow. Before extracting one, check whether the paths describe ordinary documents or a larger system tree. Opening the archive does not tell you where its files ought to be installed.
For a file named Backup.cpio in Downloads:
cd ~/Downloads
tar -tf "Backup.cpio"
Use your actual filename. Although the command is called tar, the macOS implementation reads supported CPIO variants too. This is a libarchive/bsdtar workflow; do not assume GNU tar on another operating system has the same format support.
Kernir's project fixtures include newc and odc CPIO examples. These are different encodings of CPIO rather than different document types. A specific variant or damaged input can still fail in a particular reader.
Extract into an empty directory
mkdir "CPIO output"
tar -xvf "Backup.cpio" -C "CPIO output"
Choose another destination if that directory exists. Keep the extraction separate from system directories and existing projects: matching files can be replaced, and a backup's paths may not belong in their original locations on this Mac.
You do not need administrator privileges just to copy ordinary readable archive entries into your own new folder. Restoring ownership, device entries or a whole system is a different operation from opening documents. This guide covers inspection and extraction, not a complete backup restoration procedure.
Check that the command finished successfully. If the archive contains links, the extracted layout can depend on what the reader and destination filesystem support. Copying one document out is not proof that every metadata detail in a backup was restored.
Browse it in Kernir
The Mac download is coming soon. You can view the source and build instructions on GitHub. These steps describe the current app workflow.
Choose File › Open… (⌘O) and select the CPIO. Browse its tree, select files or folders, then choose File › Extract… (⌘E). Use the original folder structure when the documents refer to one another by relative path.
CPIO is read-only in Kernir. File › Save As… (⇧⌘S) can create a copy in a supported writable format such as ZIP or TAR, but it cannot write another CPIO. A copy in a different format may not carry every filesystem property of the source.
Compressed and nested CPIO
A CPIO stream can be wrapped in compression or stored as a payload inside another package. The outer filename may therefore describe gzip or a package container rather than the CPIO data itself. The GZ guide explains a decompression step when needed; XAR is another container you may encounter.
If the reader cannot open the input, identify which layer you actually have before changing extensions. Ask the producer for its format and extraction instructions. Extracting a package's payload is not equivalent to running its installer.
Kernir.dmg, signed and notarized. Requires macOS 14 or later.
Related guides
App steps were checked against Kernir source code. Command examples were checked with test archives on Linux using libarchive and the named utilities, not in a new macOS session. Updated .
