To import photos from a ZIP archive on Mac, expand it in Finder, then import the extracted images into Photos. Use a separate working folder for each archive, review the import, and check Photos’ storage setting before removing the extracted files.

This guide covers one local ZIP file that has already arrived on your Mac. Finder and Photos provide the complete desktop workflow. The Shortcuts sections explain how to check an existing automation’s file types and command-line input without assuming that an archive, a folder, and an image are interchangeable.

Prepare a separate folder for this archive

For an illustrative practice run, use disposable PNG images of plain colored squares named blue-square.png and green-square.png, packaged in sample-images.zip. These are example filenames and prerequisites, not files supplied with this article.

Start with a new, empty working folder and place the ZIP inside it. This is a practical way to separate one incoming batch from previously extracted files. If your proposed folder name already exists, choose another name rather than reusing that folder.

Keep three stages distinct: the ZIP is the incoming package, the expanded files are the import source, and Photos is the destination library. Completing one stage does not demonstrate that the next stage has finished. This distinction also gives you a useful place to investigate if the final result is incomplete.

Before importing a batch you intend to remove from Finder afterward, open Photos, choose Photos > Settings, and select General. Check whether Copy items to the Photos library is selected. Apple explains that deselecting it leaves imported files in their original locations as referenced files. Moving or renaming those files can then prevent Photos from locating them. Change where photos and videos are stored on Mac.

Expand the ZIP in Finder

Double-click the ZIP in your working folder. Apple documents that the expanded item appears in the same folder as the ZIP. Wait for expansion to finish, then inspect the resulting files or folders before proceeding. Zip and unzip files and folders on Mac.

Use the actual expanded result as your next starting point. Do not build the workflow around a guessed output name such as sample-images, or assume that every archive produces exactly one enclosing folder. The useful check is whether the images you intend to import are present in the working folder’s extracted contents.

Apple’s Finder instructions do not specify a universal replacement or renaming policy for every extraction name collision. The separate-folder approach avoids depending on such a policy when an earlier batch has similarly named files. It does not resolve duplicate names or other structural problems already inside the archive.

If expansion fails, stop at this stage. Apple recommends checking that the Mac has enough space for the expanded item; an archive received from elsewhere may also need to be created and sent again. Renaming its extension is not a substitute for obtaining a usable ZIP. Apple’s ZIP troubleshooting guidance.

Import the extracted images into Photos

With expansion complete, follow Apple’s documented local-storage import route:

  1. Open Photos and choose File > Import.
  2. Select the extracted images or their folder, then click Review for Import.
  3. Use the Album menu to choose the destination. For a folder containing other folders, choose Library.
  4. Select the images you want and use the selected-items import button, or click Import All New Photos.

These steps import the extracted content, rather than using the ZIP as the photo source. Import from storage devices and DVDs in Photos on Mac.

If preserving a nested folder arrangement matters, Apple documents the Keep Folder Organisation option during folder import. A group of folders cannot be imported directly into an album. For a simpler batch, Apple also supports dragging extracted files or folders from Finder into the Photos window. Apple’s folder and drag-and-drop import instructions.

Review the resulting batch before repeating the import or removing its source files. For the two-image practice example, the intended result is both colored-square images visible and openable in Photos. That is an illustrative completion check, not a claim that this example was executed.

Check the four handoffs if something is missing

The following decision aid separates problems that can otherwise look like the same failed import. It is a troubleshooting sequence derived from the documented extraction, import, and storage behavior.

Checkpoint What to establish Next step if it fails
Incoming file The intended ZIP is present in your working folder. Locate the actual incoming file before continuing.
Expansion The expected image files are present in the expanded contents. Resolve extraction first; check available space or request a replacement ZIP.
Import The intended images were selected and the import completed. Return to the extracted batch and review the selection.
Storage Photos copied the images into its library, or their referenced originals remain available. Keep referenced files in place or consolidate them before cleanup.

Do not treat a matching filename as proof that two photos are identical, or a different filename as proof that a photo is new. Likewise, the label Import All New Photos should not become a promise that every possible duplicate or altered copy will be handled as you expect. Review the actual batch and resulting images.

What should you verify before using Shortcuts?

A shortcut can receive a file without receiving an image. Apple defines Files broadly enough to include ZIPs, while Images means image files and Folder is a separate input type. For an incoming archive, choosing an images-only input restriction would describe the wrong starting content. Understanding input types in Shortcuts on Mac.

Preserve those distinctions throughout an automation. A path written as text, a ZIP file, an extracted folder, and individual image files represent different handoffs. Before connecting steps, establish what the previous action actually produces and what the next action accepts.

Apple provides a concrete way to inspect this on your Mac: open the shortcut, Control-click an action’s icon, and choose Show Info. The description includes its accepted input and resulting output. You can also search the action library and inspect an action’s information before adding it. Navigate the action list in Shortcuts on Mac.

Check each connection rather than relying on the action names alone. Apple explains that a connecting line indicates that an action’s output feeds the following action, and incompatible actions can appear without that connection. Some actions produce no output at all. An extraction step therefore needs its own verified output contract before you attach a saving or importing step. Action connections in Shortcuts on Mac.

For an existing shortcut, test each handoff using only the disposable colored-square batch. Apple recommends placing Quick Look between actions to see the content flowing through the shortcut. Check the item types and contents before allowing subsequent actions to proceed. Testing your actions in Shortcuts on Mac.

These public guide pages explain how to verify actions; they do not establish the complete extraction-and-Photos-import action contract for every installed Mac. Consequently, this article does not present a guessed end-to-end action chain. If an action’s availability, output type, existing-file behavior, or collision handling is unclear, use the Finder and Photos procedure above to finish the task.

Does the Shortcuts command line change the workflow?

The command line can launch an existing shortcut. It does not create that shortcut’s actions or supply an import behavior the shortcut lacks. Apple documents shortcuts list for checking which shortcuts are available:

shortcuts list

This command requires macOS with Shortcuts available. It lists shortcuts; it does not extract or import the sample archive. Run shortcuts from the command line.

For a shortcut you have already built and tested, Apple documents -i or --input-path for passing file paths. Piping a pathname into the command instead treats that pathname as text. The input file must actually exist, and the receiving shortcut must handle the supplied content. The flag neither creates a missing archive nor resolves an output-name collision. Apple’s command-line input documentation.

Keep command completion separate from task completion, too. Apple documents exit status 0 for a successful shortcut run and 1 for an error; a shortcut that asks for input pauses for that interaction. A successful run still needs the intended final behavior to be part of the shortcut. Confirm the images in Photos before considering the batch finished. Apple’s shortcut execution documentation.

Finish the batch before cleaning up

If Photos imported the files as referenced items, retain their source folder. To bring selected referenced files into the library, Apple documents selecting them in Photos, choosing File > Consolidate, and clicking Copy. Changing the import setting alone should not be used as evidence that an earlier referenced batch has been consolidated. Copy referenced files into a photo library.

Finish by checking the intended images in Photos and confirming where their originals are stored. Keep the ZIP and extracted batch until those checks are complete. For an ordinary incoming archive, a separate working folder, Finder expansion, and a reviewed Photos import provide a clear path from the received package to usable library images.

Sources