Cannot open the illustration. The file is locked or in use by another applicatio

Illustrator macOS: 'File Locked or In Use' Fix Guide

That locked-file error in Illustrator on macOS usually means a background process or stale lock is holding your AI file. Here's how to free it fast.

I know this error is infuriating. You double-click an AI file you were working on yesterday, and Illustrator throws "Cannot open the illustration. The file is locked or in use by another application." No preview, no hints. Just a wall.

Here's the thing: Illustrator on macOS doesn't actually lock your file most of the time. This error is usually a stale advisory lock — a little flag in the file system that says "someone's working on this" and never got cleared when the last app crashed. Nine times out of ten, the culprit is a zombie Illustrator process or a cloud sync daemon fighting over the file. Let's fix it.

Cause 1: A zombie Illustrator or preview process still holds the lock

This is the one I see most often. You force-quit Illustrator yesterday after a hang. macOS thinks it's gone. But a background helper — usually AdobeIPCBroker, CCLibrary, or a stuck illustrator process — is still running and still holding the file handle.

How do you know? Open Activity Monitor (Command-Space, type "Activity Monitor"). Search for Illustrator. If you see anything there while Illustrator isn't visibly open, that's your problem.

Kill it from the terminal — faster and more thorough than Activity Monitor:

pkill -f "Adobe Illustrator"
pkill -f "AdobeIPCBroker"
pkill -f "CCLibrary"
pkill -f "Creative Cloud"

Then wait ten seconds and try again. Don't just reopen — wait. macOS takes a beat to release file descriptors after a process dies.

If the file still won't open, there's a second layer: the resource fork and the .lock sidecar. On older AI files that lived on a network share, you'll sometimes find a hidden file next to yours named ~yourfile.ai or .~lock.yourfile.ai#. Delete it:

ls -la ~/Documents/YourProject/
rm -f .~lock.*.ai#

Also check permissions while you're in Terminal. If the file is owned by root because you once opened it from a mounted disk image or a Time Machine backup, Illustrator (running as you) can't lock it. Fix:

sudo chown $(whoami):staff ~/Documents/YourProject/yourfile.ai
chmod 644 ~/Documents/YourProject/yourfile.ai

Cause 2: iCloud Drive or Dropbox is mid-sync

This one trips up everyone who works from ~/Desktop or ~/Documents, because since macOS Catalina those folders are mirrored to iCloud Drive by default. If the file is syncing — even a background metadata sync — the bird daemon (that's the real process name for iCloud Drive on macOS) holds a lock that Illustrator reads as "in use by another application."

The tell: the file shows a little cloud icon in Finder, or the Finder status bar says "Uploading X items." Wait for it to finish. If you're impatient:

killall bird
killall cloudd

They'll respawn on their own. Then try opening the file.

Dropbox behaves the same way — its Dropbox Helper process grabs an exclusive lock during upload or when Smart Sync is downloading a placeholder file. Right-click the file in Finder and check if it says "Make available offline." If it does, click that and wait for the full download before opening.

My honest opinion: don't keep working AI files in iCloud Drive or Dropbox. Native Illustrator files are complex, they use resource forks, and cloud folders corrupt them more often than people admit. Keep an active project on a local folder like ~/Illustrator/ and let Time Machine handle backup. Sync the exported PDF/PNG when you're done.

Cause 3: The AI file itself is damaged or was opened in the wrong app

If the two fixes above don't work, the lock isn't the problem — the file is. This happens most with files that were emailed, downloaded through a browser, or moved from an older macOS version where HFS+ resource forks got mangled during transfer. When the file's internal structure is broken, Illustrator can't read the header and reports it as "locked" because that's the closest error it has.

Test it quickly. Duplicate the file, rename the copy to test.pdf, and try opening it in Preview. Adobe AI files are PDF-compatible at their core. If Preview opens it, the data is intact and the problem is a permissions or resource fork issue — go back to Cause 1. If Preview also fails, the file is corrupt.

What to try, in order:

  1. Open Illustrator, then use File > Open from inside the app instead of double-clicking. Sometimes the launch handler is the broken link, not the file.
  2. Open the previous autosave from ~/Library/Application Support/Adobe/Adobe Illustrator [version]/en_US/Recover/. Illustrator keeps up to three recent autosaves there.
  3. Restore from Time Machine or your backup. Right-click the file in Finder, choose Enter Time Machine, and pick a version from before the corruption.
  4. If you have Creative Cloud, log into assets.adobe.com — your cloud documents keep version history for 60 days on most plans.

One more thing people miss: if you double-clicked an AI file and macOS opened it in Photoshop or Preview by mistake, that app now owns the file type association and sometimes leaves a lock behind. Right-click the file, Get Info, and check "Open with." Set it to Adobe Illustrator and click "Change All." Then kill the rogue app:

killall "Adobe Photoshop"
killall Preview

Quick-reference: match symptom to fix

SymptomLikely causeFix
Illustrator not visibly open, error on openZombie process holding handlepkill -f "Adobe Illustrator", wait 10 sec
File has cloud icon in FinderiCloud/Dropbox mid-syncWait for upload, or killall bird
File came from email/downloadCorrupt resource forkTest as PDF in Preview, restore from backup
Owned by wrong userPermissions from external disksudo chown $(whoami):staff file.ai
Opens in Photoshop/Preview insteadWrong default appGet Info > Open with > Illustrator > Change All
Hidden .~lock file presentStale lock sidecarrm -f .~lock.*.ai#
Nothing works, file won't previewFile is damagedRestore from Recover folder or Time Machine

Start at the top. Zombie processes fix 80% of these cases in under a minute. Cloud sync covers most of the rest. Only after both fail should you assume the file itself is gone — and by then you've ruled out everything cheap, which is exactly the order you want.

Related Errors in Software – Adobe Suite
The file has an unsupported compression type Premiere Pro 'Unsupported Compression Type' on MP4 Import CR_E Adobe Suite CR_E internal error: the font cache fix that works Unable to allocate 0.000 MB of memory After Effects "Unable to allocate 0.000 MB" Memory Error Fix Adobe ID stuck in redirect loop on login

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.