Copy Netpbm Images into PAM Format with pamtopam

Some downstream tool insists on a PAM file, and all you have is a PBM, PGM or PPM: pamtopam does that one conversion and nothing else. It reads any Netpbm image on standard input and writes a PAM stream on standard output, so the whole job is a redirect either side of the command.

• Time: a couple of minutes.
• Needs: a shell, a readable Netpbm image, and write access to the destination directory.
• Skip sudo: this is an unprivileged copy. Only reach for it if file permissions genuinely block you.

Examples below use the locally installed Netpbm 11.5.2, from package netpbm 2:11.05.02-1.1build1.

1. Check the installed command

Find out which binary your shell will actually run, and pin down the version, before you build anything on top of it:

$ command -v pamtopam
/usr/bin/pamtopam
$ pamtopam --version
pamtopam: Using libnetpbm from Netpbm Version: Netpbm 11.5.2

The extra build-information lines after the version number vary between package builds; ignore them. What matters is fixed: pamtopam reads standard input and writes standard output, full stop.

2. Convert with standard input and output

Point the source in from one side and the destination out the other:

$ pamtopam < /path/to/source.ppm > /path/to/output.pam

The .ppm in the filename is just a label; pamtopam reads PBM, PGM, PPM or PAM input equally well, and always writes PAM out. It does not resize, recolour or clean up the picture in any way, it only repackages the same pixels into a different container.

There are no pamtopam-specific flags to reach for here. Do not go hunting for an output option or an input-filename position, neither exists. The common libnetpbm options may technically be recognised, but you will not need them for a plain copy.

$ pamtopam < /path/to/source.ppm > /path/to/output.pam
$ printf 'exit status: %s\n' "$?"
exit status: 0

3. Verify the result is really PAM

A quick sanity check with file before you hand the output to anything else:

$ file /path/to/output.pam
/path/to/output.pam: Netpbm PAM image file, size = 640 x 480

Dimensions and exact wording depend on your input and your file version, but the important part is the same: it identifies as a Netpbm PAM image with the dimensions you expect.

For scripts, or when you want to be certain, read the header bytes yourself. Every PAM file opens with the magic number P7:

$ head -n 8 /path/to/output.pam
P7
WIDTH 640
HEIGHT 480
DEPTH 3
MAXVAL 255
TUPLTYPE RGB
ENDHDR

Do not assume these exact values for every file. A greyscale source gives depth 1 and a different tuple type; a higher-precision source gives a different maxval. Check the header fields against what your source image actually is, not against this example.

4. Stop a failed conversion wiping the old file

Here is the sting: shell redirection truncates the destination before pamtopam even starts. That is fine for a new file, and dangerous when /path/to/output.pam already holds something you need:

$ pamtopam < /path/to/source.ppm > /path/to/output.pam

If the source turns out to be corrupt, your old destination can already be gone, replaced by a half-written file. Write to a temporary name in the same directory, check it, then rename it into place:

$ pamtopam < /path/to/source.ppm > /path/to/output.pam.new
$ file /path/to/output.pam.new
/path/to/output.pam.new: Netpbm PAM image file, size = 640 x 480
$ mv /path/to/output.pam.new /path/to/output.pam

5. Diagnose input and output failures

Path or permissions problem on the input? Check it directly, without touching anything:

$ ls -l /path/to/source.ppm
$ test -r /path/to/source.ppm && echo readable
readable

A bad magic number message means the first bytes are not a PBM, PGM, PPM or PAM header, which usually means a text file, a compressed file or an unrelated binary landed in the wrong place. Do not paper over this by renaming the file. Identify the real format first, then decompress or convert it properly before you try pamtopam again.

If the command exits non-zero, treat whatever it produced as untrusted. Check the status and inspect the temporary file before anything downstream touches it:

$ pamtopam < /path/to/source.ppm > /path/to/output.pam.new
$ status=$?
$ printf 'pamtopam status: %s\n' "$status"
pamtopam status: 0
$ test "$status" -eq 0 && file /path/to/output.pam.new

Do not reach for root to hide a permissions problem here. Fix directory ownership and permissions instead. If the output directory belongs to a service or is shared with other users, agree its ownership and replacement policy before you start writing files into it.

6. Know when pamtopam is the wrong tool

pamtopam is a narrow format adapter, not a general image editor. Reach for it only when the next program in your pipeline specifically needs a true PAM file. Need a more general PAM or PNM translation? The manual points at pamchannel instead. If that next program is happy with your original PBM, PGM or PPM directly, skip the conversion step entirely.

Its output is binary image data, even though the PAM header reads as plain text. Never open it in a text editor, pipe it through anything that touches whitespace, or assume that copying the header alone copies the image. Keep the original input around until whatever consumes the PAM file has actually accepted it.