Mac Slow When Importing From a Camera? Try These Fixes

Plug a camera into a Mac and a chain reaction starts. Photos may auto-launch. Image Capture may pop up. ImageCaptureCore frameworks start communicating with the camera. macOS attempts to read every image’s metadata. iCloud Photos, if enabled, prepares to upload. Spotlight prepares to index. Time Machine notes the new files for backup.

For a small import — a few dozen photos from a phone — none of this is noticeable. For a real import — a memory card full of RAW files from a shoot — it can lock up your Mac for an hour. Worse, the slowdown often persists after the import completes, because the post-import processing keeps running in the background.

What Happens During a Photo Import

When you import to the Photos app, several processes work simultaneously:

• Photos — the main app, handles UI and library writes
• photoanalysisd — analyzes faces, scenes, and objects
• photolibraryd — manages the library database
• mediaanalysisd — processes Live Photos and videos
• cloudphotosd — uploads to iCloud Photos if enabled
• mds_stores / mdworker_shared — Spotlight indexing the new files
• bird / cloudd — iCloud Drive coordination if folders sync

Open Activity Monitor during a heavy import. You’ll see most of these at significant CPU. On a 16GB Mac, combined memory use can hit 6-8GB.

The single heaviest is usually photoanalysisd. It runs face detection, object recognition, and scene classification on every image. For RAW files, it has to first decode the RAW (which is its own CPU cost) before analyzing.

Free up RAM in one clickSweep frees inactive memory and pauses runaway processes. Get Sweep free →

Why RAW Files Specifically Tank Performance

RAW files are large (40-80MB each for modern cameras) and expensive to decode. macOS has a RAW decoder for most camera makers, but it’s CPU-intensive.

Compounding the problem:

1. Photos generates JPEG previews for every RAW immediately
2. Quick Look generates thumbnails at multiple sizes
3. Faces analysis decodes the RAW yet again
4. Memories analysis runs on the new content

For a typical wedding shoot of 2,000 RAW files, the post-import processing can run for 6-12 hours on a Mac that isn’t extremely fast. During that time, opening Photos feels sluggish, and the rest of the system is slower than usual.

Image Capture: The Lighter Alternative

If Photos feels too heavy for your import workflow, Image Capture (Applications > Image Capture or /System/Applications/Image Capture.app) is a lighter option that’s been on macOS for years.

Image Capture:

• Doesn’t run face/object analysis
• Doesn’t add files to a managed library
• Imports to a folder of your choosing
• Lets you delete from camera after import

For professional photo workflows, the typical pattern is:

1. Import with Image Capture to a destination folder (or a structured archive folder)
2. Process in Lightroom or Capture One — both manage their own catalogs
3. Skip Photos entirely for serious work

Photos is great for personal snaps. For high-volume imports, especially RAW, Image Capture or a dedicated catalog tool is faster and lighter.

Why Imports Stall Mid-Way

Sometimes a Photos import seems to hang at, say, 1,847 of 2,000 photos. It’s not actually frozen — it’s processing.

Common stall causes:

1. A specific corrupt file — Photos may retry it before moving on
2. A file with weird metadata — older cameras or modified files
3. Memory pressure — Photos pauses to wait for RAM
4. A duplicate that Photos is checking against your library
5. iCloud Photos verifying before allowing the import to proceed

Close Photos, wait 30 seconds, reopen. The library will resume from where it stopped. If a specific file is the culprit, Photos may flag it and skip on the next attempt.

Memory and Disk During Import

A 64GB SD card of RAW files can be 40GB once imported. Photos copies them into the Photos Library package (~/Pictures/Photos Library.photoslibrary). The original files in the package don’t disappear — they’re stored in originals/.

Before import, verify:

• At least 1.5x the import size in free disk space — for working space
• At least 4GB of free RAM ideally — heavy imports under memory pressure are painful
• Time Machine isn’t running — it’ll fight for disk I/O

If your Mac is short on space, Photos imports can fail mid-way with cryptic errors. Sweep finds large unused files and old downloads that often free up enough space to make imports succeed.

iCloud Photos: The Multiplier

If iCloud Photos is enabled, every imported file uploads to iCloud after the import completes. This:

• Uses bandwidth, which is fine
• Uses cloudd CPU and memory, which can be substantial
• Triggers Photos analysis on every other device that has the same iCloud Photos library

For a heavy import, your iPhone, iPad, and other Macs all suddenly start doing analysis work. If you have a Mac that’s plugged in and idle, it’ll handle most of the analysis. If you only have a MacBook on battery, the analysis competes with whatever you’re doing.

To temporarily disable iCloud Photos sync during a major import: Settings > Apple ID > iCloud > Photos > toggle off “Sync this Mac.” Re-enable when import is done. Be aware that toggling off may cause your library to start downloading “originals” you’d previously offloaded — proceed carefully if you’re space-constrained.

Skip the manual huntSweep finds the buildup slowing your Mac and clears it in seconds. Download Sweep free →

Settings Worth Changing for Heavy Photo Workflows

In Photos > Settings:

• iCloud > Sync this Mac: OFF during major imports, ON otherwise
• iCloud > Optimize Mac Storage: OFF for active editing workflows — keeps originals local
• General > Importing > Copy items to the Photos library: ON for safety, OFF if you’re a Lightroom user managing originals separately

In macOS:

• System Settings > Battery > Optimize video streaming while on battery: OFF if importing from camera connected by USB-C while on battery (rare combination but matters)
• System Settings > Energy / Battery > Power Adapter > Prevent automatic sleeping when display is off: ON during imports so Photos can finish processing

Image Capture Settings

In Image Capture itself:

• Click the small arrow at the bottom-left to expand options
• Set the import destination explicitly
• Choose “Import All” or select specific files
• “Delete after import” should be off by default — leave files on the card until you’ve verified backup

For automated workflows, Image Capture has built-in actions you can configure to run on import (open in app X, copy to folder Y, etc.).

Pause runaway processes safelySweep identifies the apps actually eating your CPU and lets you pause them without losing work. Free for macOS →

A Diagnostic for Slow Imports

When importing photos drags your Mac:

1. Check Activity Monitor. Note photoanalysisd, photolibraryd, mediaanalysisd
2. Check disk free space. Imports need significant headroom
3. Check whether Photos auto-launched — Image Capture is lighter
4. Check iCloud Photos status — uploads compound CPU use
5. Pause iCloud Photos sync for the duration of major imports
6. Quit other heavy apps — Photoshop, browsers, Slack
7. Plug in to power — battery throttles compound the slowdown
8. After import, let analysis finish overnight — Plug in, leave the lid open, lock the screen

After-Import: Letting Analysis Finish

After a heavy import, photoanalysisd will run for hours. It runs at low priority and tries to use idle time. If you actively use your Mac the whole time, analysis takes longer.

For best results:

1. Finish the import
2. Plug in the Mac
3. Leave it overnight, screen locked, lid open (closing the lid suspends most background work on portable Macs)
4. Check the bottom of the Photos sidebar in the morning — if analysis is done, the message will be gone

If you don’t give Photos this idle time, analysis can drag for days, with the Photos process spiking CPU whenever the Mac is unused.

Workflow Patterns That Save Time

A few patterns work well for high-volume photo imports:

• Use a dedicated drive for originals. Don’t import to your boot drive
• Process in Lightroom or Capture One. Their catalogs are more efficient than Photos for thousands of files
• Cull aggressively before import. Don’t import 1,500 photos when you’ll only keep 200
• Use Image Capture for raw transfer, then a real catalog tool for management
• Don’t sync RAW files to iCloud Photos. It’s not designed for it

Photos is fine for everyday phone uploads. Heavy professional workflows benefit from tools designed for the job. Sweep keeps the macOS side healthy regardless — old caches, language files, and orphan downloads cleared so when you do a heavy import, your Mac has the headroom it needs to finish without dragging everything else along with it.