AI File Viewer

An AI file viewer should prove what kind of AI file it received

The letters .ai can describe several generations of Adobe Illustrator files. Some modern files include a complete PDF-compatible representation; older or deliberately noncompatible files can instead depend on Illustrator-specific or PostScript data. A filename does not reveal which one you have. This viewer checks the bytes for both a valid PDF document and structural Illustrator identity before it offers a preview.

That distinction is the product boundary. A normal PDF renamed with an AI extension is not labeled an Illustrator file. An EPS or PostScript program is not sent to a speculative interpreter. A native AI file without the verified PDF representation receives an explicit unsupported result rather than a blank canvas or a picture that only happens to look plausible.

Preview the compatible representation, not an invented layer model

The preview comes from the PDF-compatible content stored in the source. It can show the appearance that the authoring application saved for compatible PDF readers, but it does not reconstruct Illustrator layers, linked assets, brushes, live effects, editable text, or an artboard panel. Those authoring features may exist in private document data without being available as independent controls in a PDF renderer.

Documents with more than one compatible page expose the page count and a visible page selector. Page one may be selected initially, but it never silently stands for the entire file. Page dimensions and rotation are reported before export, so choosing a landscape artboard-sized page is a deliberate action rather than a surprise discovered after download.

PNG and PDF answer two different handoff needs

PNG creates a raster image from the selected compatible page. It is useful when a website, presentation, review thread, or image editor needs pixels rather than an Illustrator source. Choose 72, 144, or 300 DPI; 144 DPI is the visible default. Rendering starts on a transparent canvas and adds no background fill. Areas the local PDF renderer actually outputs with alpha stay transparent in the PNG, but complex PDF transparency groups can be composited opaque. The preview shows that rendered result before download. This is not a universal promise that every transparency effect stored by Illustrator becomes PNG alpha. The receipt names the selected page, output dimensions, renderer-alpha handling, and rasterization setting. The result is not vector artwork and cannot recover editable paths, type, swatches, or layer names.

PDF keeps the full verified compatible document, including its complete page order, rather than turning only the current preview into a one-page substitute. The downloaded PDF is a compatibility copy, not a claim that Illustrator-specific editing data was normalized, cleaned, or made portable. Keep the original AI file whenever someone may need to continue editing, relink placed artwork, substitute fonts, inspect spot colors, or prepare production separations.

Active PDF behavior is blocked before anything is shown

PDF-compatible does not automatically mean passive. A PDF can contain JavaScript, automatic actions, launch instructions, external URI actions, forms, XFA, RichMedia, attachments, or embedded files. V1 recursively rejects those structures before preview and export. It does not execute document code, open a link on behalf of the file, fetch a remote resource, or repackage active content under a fresh PDF filename. Encrypted input is unsupported rather than opened with a password prompt.

Encryption, malformed object graphs, truncated streams, impossible page geometry, and local resource pressure also receive distinct messages. These checks are intentionally stricter than asking whether a PDF library managed to draw something. A partial render can look convincing while omitting the exact object that made the document unsafe or incomplete.

This is not a general Illustrator, EPS, or PostScript converter

Older AI formats and EPS can contain PostScript programs that require a substantially different interpreter and security model. Supporting the file extension while ignoring that distinction would turn an honest compatibility viewer into a format lottery. This route therefore stops at the independently verified PDF-compatible subset and names unsupported input without guessing.

If the actual source is SVG and the job is to reduce or inspect its markup, use the SVG optimizer. If it is a Photoshop PSD or PSB with a stored composite, the PSD viewer has a separate format contract. A PDF that was never an Illustrator file belongs in a PDF workflow such as PDF to PNG, not behind a renamed extension.

The receipt separates preserved bytes from rendered pixels

Before export, Document details reports Source format, PDF version, Artboards, Illustrator identity, Identity location, Private data streams, Safety, and File size. The result receipt separates Source artboards, Selected artboard, Output format, Dimensions, Resolution, Alpha, Background, Color handling, Illustrator private data, Safety, File size, and Reopened. Those rows make a flattened PNG distinguishable from a byte-preserving PDF without relying on the extension or button label.

The PNG receipt says which artboard was rasterized, confirms the reopened dimensions, and distinguishes preserved renderer alpha from the absence of an added background fill. Its untagged browser RGB canvas may use an ICC profile while rendering, but that profile is not embedded in the result. The PDF receipt instead says that all artboards remain in source order, original page boxes and color data are preserved, private data is preserved byte for byte, and the downloaded structure reopens locally.

Metadata and Illustrator private data are not described as cleaned merely because the extension changes. If a separate PDF needs a metadata-cleaning pass, use the PDF metadata remover and read its preservation contract first. Removing authoring data can make a file unsuitable for later editing, so it is never smuggled into this viewer as a silent side effect.

Your document stays in this browser tab

AI is a binary file format, so the honest intake is a local file picker or drop rather than a text box or image paste target. Inspection and rendering run locally. The source bytes, filename, preview, page facts, and generated downloads are not sent to a conversion API, placed in the URL, saved in browser storage, or attached to analytics.

The renderer may lazily fetch its own fixed, self-hosted code and font or color resources from this site after a file is chosen. Those assets are the same for every visitor and contain no part of your document. The local-processing guide explains how to distinguish those static requests from an upload. Large files receive memory advice before work begins, and cancel, reset, or a newer file prevents stale output from becoming the next download.