Preview, the viewer that reads dead formats and edits what it shows
Measured on macOS 27: Preview opens 50 document types, still reads MacPaint and FlashPix, holds Apple's default-PDF flag, and runs as one helper-free process.
By Chethan Kumar S N · Updated
Preview is the app every Mac has and almost nobody opens on purpose. It is the viewer: the program that appears when you double-click a PDF, a screenshot, a photo from a camera card, or some file you downloaded a decade ago and double-clicked today. It draws no attention to itself, it has no storefront, and on the Mac measured for this page it had been sitting open for five days, running as a single process using 5.7 MB of memory, doing nothing at all.
The machine in question runs macOS 27 with a login session about thirty days old. Preview was started by its owner on Saturday 14 November at 16:30 and never quit. In that time it consumed, cumulatively, so little processor that ps reports 0.0 percent. That restraint is the through-line of everything below, because under the quiet surface this app is one of the strangest inventories in the whole system folder.
A real folder, not a pointer
The Safari page in this series opened with a trick: the app in the Applications folder was a 54-byte symbolic link pointing into a sealed system volume, and the real browser lived somewhere else entirely. Preview is the counter-example. Look for it and you find an actual directory:
$ ls -la /System/Applications | grep Preview
drwxr-xr-x 3 root wheel 96 Sep 24 12:40 Preview.app
A real folder, owned by root, on the sealed system volume. The whole app is 6.3 MB, and the main executable inside it is 7,357,792 bytes, built for two architectures at once, arm64e and arm64e.x1. Its version.plist gives version 11.0, build 1147, and an internal project name that reads, simply, Preview. Same pattern as Safari: the project name is the product name. Apple’s engineering names leak through on the small apps; the big front-facing apps get to be themselves.
The signature says the rest. The app is signed with the hardened runtime flag, it carries the App Sandbox entitlement, and the signing timestamp reads 9 August 2026. It cannot be modified, it updates only when the system volume updates, and dragging it to the trash is not an option you will be offered, because there is no user-writable copy anywhere. Your own Applications folder, checked on this Mac, contains zero Preview apps.
Fifty doors in, ten of them editable
What makes Preview worth a page is not the app. It is the list of things the app claims it can open. Apple documents this in the app’s own information property list, and on this machine the list runs to 50 document types covering 58 uniform type identifiers. The split is the story: 40 of the 50 are declared Viewer, meaning Preview will show you the file, and 10 are declared Editor, meaning it will also let you save changes back to it.
The editor list is the classic bitmap family: PDF, JPEG, PNG, TIFF, BMP, GIF, TGA, SGI, ICNS and JPEG 2000, plus an Apple-internal variant called rJPEG. Everything else is view-only. And on the PDF entry Apple sets one more flag, LSIsAppleDefaultForType, which is the operating system formally writing its own viewer into the default seat for PDF files. You can install another PDF app and change the default, but out of the box, PDF means Preview.
Then there is the viewer list, and it reads like a museum donor wall:
com.apple.macpaint-image, the bitmap format of the original Macintosh paint programcom.apple.pictandcom.apple.rjpeg, two more Apple formats younger users have never metcom.kodak.flashpix-image, a format identified by its maker’s name, Kodakcom.compuserve.gif, an identifier carrying the name of the service that introduced itcom.ilm.openexr-image, the identifier initials spelling out a visual-effects studiocom.adobe.illustrator.ai-imageandcom.adobe.photoshop-image, the working files of two Adobe appscom.google.webp,com.apple.icns,com.apple.localized-pdf-bundle, evencom.apple.pdf-printer-settings
The makers behind several of these identifiers no longer exist as they did. Preview still opens their files. There is a quiet public-service argument in that: every Mac is a working reader for formats whose originating software you cannot buy, which is more than can be said for most of the machines that created them.
The editor hiding in the viewer
The property list says what Preview may open. Its menus say what it does. The interface files inside the app hold the strings the menus are built from, 180 of them in the main menu alone, and reading the list is like reading a feature sheet: Import from Scanner…, Signature, Export as PDF…, Annotate, Highlight Text, Show Magnifier, Assign Profile…, Thumbnails, Highlights and Notes.
The deeper tell is the undo vocabulary. Preview ships 68 separate undo strings, things like Add Highlight, Extend Highlight, Highlight Style and Text Annotation Style. Undo strings exist for actions you can perform, so the undo list is a confession: this viewer expects to be written in. Apple’s own Preview User Guide says the same thing in one line: you can use Preview to fill out PDF forms and even add a signature.
The full string inventory runs larger than most apps’ whole interfaces: 816 localisable strings in the main table, spread across more than 60 interface files, with names that sketch the app’s corners. There is a scanner view that runs inline. There is an image colour adjuster. And there are two views whose names postdate everything else in the app: a Hydra view and a C3D file inspector, interface files for image work that did not exist when Preview got its name, now living beside the MacPaint reader.
The entitlements are a map of alliances
Every signed app carries an entitlements list, the privileges it asked for and was granted, and Preview’s is a strange read for a viewer. It holds the Maps entitlement. It holds an Apple Books entitlement. It holds an iCloud Drive container identifier. And its image-decoding permission list includes entries for HEIF, the modern photo format, and for DICOM, the format medical imaging is stored in.
None of this is a scandal; it is a receipt. The app draws map imagery, annotates books that sync their notes, writes to iCloud Drive, and decodes camera and scanner formats from hospitals as well as phones. The frameworks it links tell the same story from the other side: PaperKit and a private AnnotationKit for marking up documents, VisionKitCore for understanding what is in an image, Metal for drawing, and OpenGL, which Apple has spent years telling developers to leave, still linked in macOS 27 by the app that has to open every legacy file you throw at it. A viewer this old does not get to be tidy.
One process, no entourage
Here is the measurement that separates Preview from nearly every other page in this series. On a Mac with a thirty-day session, Preview runs as exactly one process:
$ ps -Awwo pid,ppid,user,%cpu,rss,etime,args | grep "[P]review.app"
43179 1 chethankumar 0.0 5840 5-00:41:07 /System/Applications/Preview.app/Contents/MacOS/Preview
Parent process 1, launchd, which is how every GUI app starts. Five days and forty-one minutes old at the moment of measurement. 5.7 MB of memory. No helper processes, no XPC services of its own, no agents, nothing running under its name while it is closed. The Safari measured on this same machine kept thirty-five processes alive with the browser shut; Preview keeps none, ever. Its sandbox container folder, ~/Library/Containers/com.apple.Preview, existed on disk with an empty data directory inside, and the classic preferences domain for the app does not exist at all, because a viewer this undemanding had nothing to write down.
One neighbour causes the confusion worth clearing up. Press the space bar on any file in Finder and a different system, Quick Look, shows you a preview without opening anything. Its preview-generation extension, measured on this Mac, had been running for ten days under the Quick Look framework, separate from the Preview app and its process. That is the “preview” that never dies, and it answers to the system. Preview the app answers to you: quit it and it is gone, having cost five megabytes for its trouble.
The bill
| Reading | Value |
|---|---|
| The app | a real 6.3 MB folder in /System/Applications |
| Version | 11.0, build 1147, signed 9 August 2026 |
| Architectures | arm64e and arm64e.x1 |
| Document types declared | 50, covering 58 type identifiers |
| Viewer roles | 40, from Illustrator to MacPaint |
| Editor roles | 10, PDF plus the classic bitmap family |
| Default for PDF | yes, by Apple’s own LSIsAppleDefaultForType flag |
| Interface inventory | 816 strings, 180 in the main menu, 68 undo strings |
| Notable entitlements | Maps, Apple Books, iCloud Drive, HEIF and DICOM decode |
| Running processes | one, five days old, 5.7 MB, 0.0 percent CPU |
The bill is the personality. Preview is the app Apple trusts with every orphaned file format, gives the editor’s pen to anyway, and then holds to a budget of one process and six megabytes. Your Mac has flashier apps and busier ones, dozens of them measured across the pages of this series, but none with a better claim to the word companion. When some archive hands you a 1990s image format in 2026, the viewer that opens it is already installed, and it will not even make a noise about it.
Questions
What is Preview on my Mac?
Apple's built-in viewer for PDFs and images, the app that opens when you double-click a file and nothing else has claimed the job. On the Mac measured here it is a 6.3 MB app folder in /System/Applications, version 11.0, build 1147, signed on 9 August 2026 and sandboxed. It declares 50 document types it can open, from PDF to Photoshop, Illustrator, WebP, OpenEXR and older still: MacPaint images, PICT files, and Kodak's FlashPix. Ten of those types it can also edit and save: PDF, JPEG, PNG, TIFF, BMP, GIF, TGA, SGI, ICNS and JPEG 2000. On the PDF entry Apple sets a flag called LSIsAppleDefaultForType, which is the system marking its own viewer as the default opener for PDFs.
How do I open Preview on a Mac?
It sits in /System/Applications, which Finder shows alongside your own Applications folder, so the fastest route is Spotlight: press Command-Space, type Preview, press Return. Opened with no file it shows a document picker rather than a blank page, because Preview has no new-document mode; it exists to show you files, and its File menu starts at Open. You will not find it in your own Applications folder at all, zero copies there on the Mac measured, and you cannot delete it by dragging, because /System/Applications lives on the sealed system volume macOS only replaces as a whole.
Why is Preview not opening, or not displaying a PDF correctly?
Usually the file, not the app. Password-protected PDFs prompt first, and Preview ships a dedicated password warning sheet for printing one, plus a multi-error alert for files that fail in batches, both named in its own interface files. PDFs can also carry restrictions set by whoever made them, limiting copying or printing even after the file opens, and some PDFs from other tools use features Preview renders partially. If one specific file misbehaves everywhere, it is the file; if every PDF misbehaves, open Preview directly and use File, Open, which reports what it cannot parse instead of failing silently. Activity Monitor tells you which case you are in: a single Preview process at low memory means the app is fine.
Can Preview edit PDFs?
Yes, and its own menus are the proof: Annotate, Highlight Text, Export as PDF, Show Magnifier, Signature, and Import from Scanner are all menu items in Preview's interface files, and its undo vocabulary runs to 68 separate strings, from Add Highlight to Extend Highlight. Apple's own Preview User Guide puts it in one line: you can use Preview to fill out PDF forms and even add a signature. What it is not is a page-layout tool: it edits annotations, pages and images on top of the PDF, not the original text flow inside it, which is the difference between a viewer that annotates and a full PDF editor.
Is Preview running in the background? Can I quit it?
Only if you left it open, and even then it is one process. On the Mac measured here Preview had been running for five days at 5.7 MB of memory and zero percent CPU, with no helper processes of its own; quit it and nothing of it remains. The confusion usually comes from its neighbour: Quick Look, the system that previews any file when you press the space bar in Finder, runs its own preview-generation extension that had been alive for ten days on the same machine. That one belongs to the system, not to the Preview app, and it is the one that comes back no matter what you quit.
Ready? Buy Ribbon for $15, or read all the guides.