PCX

PCX predates modern metadata frameworks entirely. Its 128-byte header stores only technical parameters — image dimensions, resolution, bit depth, and a 16- or 256-color palette — with no fields for descriptive or rights metadata. There is no support for XMP, IPTC, or embedded ICC color profiles, and the format was finalized before EXIF existed. Any metadata about a PCX asset (creator, keywords, rights, color space) has to live outside the file, in a DAM's own database record rather than the image itself.

No — PCX should not stay in active workflow use. Because tool support keeps shrinking and the format lacks color management, layers, and modern metadata, a DAM should convert ingested PCX files to TIFF or PNG for day-to-day access, previews, and downstream editing. The original PCX file is best retained only as a bit-for-bit preservation copy alongside the converted master, so provenance is documented without forcing every user to fight legacy tooling.

PCX uses a simple byte-oriented run-length encoding (RLE) applied per scanline. The two highest bits of each byte act as a flag: when both are set, the byte signals a repeat count (up to 63) for the value that follows, otherwise the byte is read as a single literal pixel value. This scheme is lossless and cheap to decode — well suited to 1980s DOS hardware — but it compresses far less efficiently than later methods like LZW or DEFLATE used in GIF, TIFF, and PNG.

PCX depth grew with each PC Paintbrush and hardware generation. Early versions targeted CGA/EGA displays with 1 to 4 bits per pixel, giving 2 to 16 colors. Later revisions added 8-bit indexed color for 256-color palettes (common once VGA became standard), and version 5, from 1991, added 24-bit true color using three 8-bit planes for roughly 16.7 million colors. A DAM may therefore encounter PCX files spanning monochrome scans through full-color images.

PCX mainly surfaces in legacy material rather than new production: scanned documents and faxes digitized in the DOS/Windows 3.x era, old CAD or engineering exports, and archives inherited from organizations that used PC Paintbrush or early Windows Paintbrush as their default editor. Manufacturing, government, and engineering archives that have been migrating systems for decades are especially likely sources, since PCX was a common default save format on those platforms.

Support is patchy but not extinct. Adobe Photoshop reads and writes PCX through a built-in plugin, and GIMP handles it natively. Lightweight viewers such as IrfanView and XnView open PCX reliably and are often the fastest way to preview or batch-convert legacy files, while ImageMagick's command-line tools can script bulk conversion. Mainstream design apps outside this small group increasingly drop PCX support, so a DAM should not assume every downstream tool in a pipeline can open the format.

ZSoft Corporation introduced it in 1985 as the native format of PC Paintbrush; it was one of the first bitmap formats on the PC and was later bundled with Windows via Microsoft Paintbrush.

No. PCX stores a single flat raster bitmap with no layer structure and no alpha channel for transparency — concepts that postdate the format's 1985 origins. Any layered artwork or image with a transparent background must be flattened before export to PCX, and that flattening is permanent; the original layer or transparency data cannot be recovered from the PCX file. For a DAM, this makes PCX unsuitable as a working format for anything requiring compositing.