AI

AI is Adobe Illustrator's native vector format, originally PostScript-based and, since Illustrator 9 in 2000, structured as a PDF wrapper around Illustrator-specific private data.

Extension

.ai

Full name

Adobe Illustrator Document

Introduced

1987, with the first release of Adobe Illustrator

Vendor

Adobe

What is inside the container

Modern AI files have a dual structure: on the outside the file is formatted as a valid PDF (when saved with the "PDF-compatible" option enabled), while Illustrator-native data describing layers, live effects, and editable paths sits inside as private, non-PDF content. This makes the PDF-compatibility setting critical for DAM interoperability — without it, non-Illustrator software cannot render the file at all. AI supports XMP metadata, embedded or linked fonts, embedded raster images, and layers.

How to open it

Windows / macOS Adobe Illustrator, native, full editing fidelity

Any PDF viewer Acrobat, Preview, or browser PDF viewers, but only if the file was saved with PDF-compatibility enabled, and only as a flattened, non-editable view

Cross-platform, third-party Inkscape, Affinity Designer, or CorelDRAW, with partial import fidelity, best results from PDF-compatible AI files

Headless / batch conversion Ghostscript-based or Adobe SDK-driven pipelines for generating raster previews at scale

For archives

For DAM archival, always save AI masters with "Create PDF Compatible File" enabled — otherwise the asset is unreadable outside Illustrator itself, defeating the point of storing it in a shared library. Keep the native AI as the editable source of truth for design teams, and generate SVG or flattened PDF derivatives for downstream systems and non-Illustrator collaborators.

Adobe shipped Illustrator for the Macintosh in January 1987, a commercial outgrowth of Adobe’s in-house PostScript font tools, and the AI format launched with it as the application’s native save format. It was a genuine gamble at the time: the Mac had limited market share, the only printer that could output Illustrator’s PostScript documents was Apple’s own expensive LaserWriter, and Bézier-curve-based drawing was an unfamiliar paradigm for most users. The format itself was PostScript-based for its first decade or so, evolving through the 1990s with the addition of Bézier curve refinements and color management.

Illustrator 9, released in 2000, changed AI’s underlying structure fundamentally by making PDF the file’s outer shell. Since then, a single .ai file contains two layers of data at once: a PDF-compatible representation that any PDF-aware tool can open and display, and separate Illustrator-native private data — layers, live effects, editable paths — that only Illustrator itself can fully interpret. Whether that PDF layer even exists depends on the “Create PDF Compatible File” option being enabled at save time.

That dual structure is the single most important fact about AI for DAM work: an .ai file saved without PDF compatibility is effectively opaque to every tool except Illustrator, which breaks preview generation, cross-team access, and any downstream automation expecting to render the asset. Enabling PDF compatibility on ingestion (or requiring it as a house standard) keeps AI files usable across a DAM’s broader toolset, while the native AI remains the right format to preserve as the editable design source.

Frequently asked

Why is the PDF-compatible setting critical when saving an AI file for a DAM?

Modern AI files are only readable outside Illustrator when saved with Create PDF Compatible File enabled; without it, non-Illustrator software cannot render the file at all, defeating the point of storing it in a shared library.

What is the dual structure of a modern AI file?

On the outside the file is formatted as a valid PDF when PDF-compatible, while Illustrator-native data describing layers, live effects, and editable paths sits inside as private, non-PDF content.

Can a non-Illustrator PDF viewer edit an AI file's layers?

No. A PDF viewer can only show a flattened, non-editable view of a PDF-compatible AI file; the editable layer and live-effect data is Illustrator-private and inaccessible outside Illustrator.

What should a DAM generate from an AI master for non-Illustrator collaborators?

SVG or flattened PDF derivatives for downstream systems and collaborators who don't have Illustrator, while keeping the native AI as the editable source of truth for design teams.

Does AI support metadata for cataloging?

Yes. AI supports XMP metadata, along with embedded or linked fonts, embedded raster images, and layers.

When was AI introduced, and how has its underlying structure changed?

AI dates to 1987 with the first release of Adobe Illustrator; since Illustrator 9 in 2000 it has been structured as a PDF wrapper around Illustrator-specific private data, rather than the original PostScript-based structure.

Which third-party tools can import AI files, and with what caveat?

Inkscape, Affinity Designer, and CorelDRAW offer partial import fidelity, with the best results coming from PDF-compatible AI files.

How can a DAM generate raster previews from AI files at scale?

Ghostscript-based or Adobe SDK-driven pipelines are used for generating raster previews from AI files in batch.

Sources

Adobe Illustrator was first developed for the Macintosh, shipping in January 1987, as a commercialization of Adobe's in-house font software and PostScript checked 2026-08-07 — Mapsoft, Adobe Illustrator Version History 1987-2026
Since Illustrator version 9 (2000), .ai files have a PDF-compatible outer structure with separate Illustrator-native private data inside, controlled by the "Create PDF Compatible File" save option checked 2026-08-07 — Datalogics, Adobe Illustrator and PDF Compatibility