An AI file won't open: five reasons, in order

24 September 2026 · Pathside guides

Pathside opens .ai, .eps, .svg and PDF on the phone →

1. The download stopped partway

The most common cause by a distance. A file that arrived over a patchy connection, or was sent through a service that truncated it, starts like artwork and ends nowhere. A viewer that checks for the end of the document will call this damaged. Ask for it again, or re-download it on a stable connection, and compare the file size with what the sender says it should be.

2. It was saved without PDF compatibility

Illustrator's Create PDF Compatible File option is on by default, and when someone turns it off the file contains only Illustrator's private data. Nothing but Illustrator can draw it. There is no fix on your side; ask for it again with the box ticked, or as a PDF.

3. It is not an .ai file

An extension is a label, not a fact. Renamed files are everywhere — a .cdr called .ai, a JPEG called .ai, a ZIP of assets called .ai. A viewer that decides from the first bytes rather than the name will tell you what you actually have.

4. The app needs a server and cannot reach one

If an app shows an error mentioning conversion, a failed request, or asks you to try again later, it was never opening the file locally: it uploads it and renders it remotely. On a weak connection it fails, and on any connection your artwork has left the device. An app that draws files on the phone has neither problem.

5. It opened fine and the artwork is white

White artwork on a transparent background, shown on a white page, is invisible. This is not a bug and there is nothing wrong with the file. A viewer that draws a transparency checkerboard shows it immediately; otherwise, try the artboard on a dark background, or export it as a PNG and look at it in a gallery.

Still stuck?

Two questions settle almost everything: how big should the file be (does yours match?), and can the sender open it themselves right now? If they cannot either, the file was broken before it reached you.

How to check the file size first

Before troubleshooting anything else, look at the size in Files and ask the sender what it should be. This one question resolves a surprising share of cases: a 12 KB file that should be 3 MB never finished downloading, and no app will ever open it. It also settles who has the problem, which saves an afternoon of blaming the wrong thing.

When only one app fails

If one viewer refuses the file and another opens it, the file is fine and the app is the problem — usually one that uploads files for server-side conversion and is failing quietly. If every viewer refuses it, believe them: the file is truncated, or it genuinely contains nothing they can read.

What "damaged" really means

Most apps say "damaged" for two different situations: bytes that stop early, and bytes that are fine but in a format the app does not speak. They are opposite problems — one needs a new copy of the file, the other needs a different app or a different export — which is why an app that names the actual reason saves you a round trip with the sender.

The fastest route to an answer

Ask the sender for a PDF export of the same artwork. It takes them seconds, it opens everywhere, and if that PDF also fails then the problem is on their side and you have proved it without an argument.