# Easy Eject Help > Official help for the Easy Eject Mac app. Covers both the website and App Store versions. Use these guides for current feature and permission behavior; ask the user to check their installed version and keep important originals. ## Guides --- Source: https://easyeject.com/help/getting-started # Get started with Easy Eject Easy Eject lives in the macOS menu bar. It recognizes many CFexpress, SD, XQD, and emulator cards even when another photo app sees a card as an ordinary drive. You can use it just to eject cards; cleaning and automatic imports are optional. ## Install the website version 1. [Download Easy Eject 1.7.6](https://github.com/rsmith4321/Ejector/releases/download/v1.7.6/Easy-Eject.dmg). It supports macOS 14 or later on Apple silicon and Intel Macs. 2. Open the disk image, move **Easy Eject** to **Applications**, then launch it. 3. Look for the eject symbol in the menu bar. The number beside it is the number of recognized physical card disks. Open the menu to see individual cards and other connected drives. The website download comes directly from GitHub Releases and is signed and notarized. Website **1.7.6** automatically checks for signed updates and asks before installing. You can check manually or disable automatic checks in Settings. Updates wait for imports, ejection and open dialogs before restarting. Users of **1.6.2 or earlier** need one manual download to get the new updater. ## Install from the Mac App Store [Get Easy Eject on the Mac App Store](https://apps.apple.com/us/app/easy-eject/id6767951388). Apple manages installation and updates, including automatic updates when enabled in your App Store settings. **The Store edition requires card authorization for cleaning and folder-based card detection.** Access is remembered, but formatting can require renewed authorization. Full Disk Access does not bypass this restriction. Some CFexpress readers need this folder access to be recognized as cards; plain eject still works without it. [Compare permissions](https://easyeject.com/help/permissions-and-versions) before choosing an edition. The public Store release is **1.1**, verified October 5, 2026, with the newer import controls and eject dialogs. ## Eject your first card 1. Connect the card reader and confirm the card appears in Finder. 2. Finish imports in Lightroom or your usual app. Wait for copying and writing to stop. 3. Open the Easy Eject menu. Choose your card under **Camera Cards** or **Emulator Cards**. If it appears under **Other External Volumes**, open its submenu and choose **Eject**. 4. Wait for Easy Eject to say the card is safe to unplug, or for it to disappear from Finder. Do not unplug after an error or while the card is busy. Plain eject needs no Easy Eject import profile or folder authorization. If a reader has two partitions, ejecting the physical disk also unmounts the other partition. Check the menu before using **Eject All Cards**. ## Where to go next - [Card detection and safe ejection](https://easyeject.com/help/card-detection-and-ejection): CFexpress recognition, same-name cards, bulk eject, and other drives. - [Clean & Eject](https://easyeject.com/help/clean-and-eject): remove hidden Mac metadata before ejection. - [Camera and device media imports](https://easyeject.com/help/air-unit-and-camera-imports): copy verified media into dated folders, with an option to leave photos for Lightroom. - [Videos first, then Lightroom](https://easyeject.com/help/video-imports-with-lightroom): use separate video and photo workflows without ejecting the card too soon. - [Permissions and versions](https://easyeject.com/help/permissions-and-versions): choose website or App Store access behavior. - [Troubleshooting](https://easyeject.com/help/troubleshooting): missing cards, denied access, or busy volumes. --- Source: https://easyeject.com/help/card-detection-and-ejection # Card detection and safe ejection ## Why CFexpress cards can be hard to eject A CFexpress reader may present a card as an external drive. Lightroom or another photo app may finish importing but not offer its usual memory-card eject control. Easy Eject lists connected storage in its menu so you can eject the card from one place. Some readers identify their hardware as CFexpress, SD, or XQD. Others use generic PCI/NVMe or USB descriptions. In those cases, Easy Eject may look for common camera folders, such as `DCIM`, before grouping a volume as a camera card. In the App Store version, folder inspection requires permission for the whole card. If a card remains in **Other External Volumes**, you can still choose **Eject** there. Easy Eject menu showing camera cards and other external volumes ## Cards with the same name Cameras often call every card **Untitled**. macOS may mount another one as **Untitled 2**. The menu can show hardware type, such as **Untitled (CFexpress)** or **Untitled (SD)**. Do not rely on the name alone before ejection. An optional import profile identifies a filesystem volume by its ID, not its Finder name or a DJI folder. If a card is formatted in camera, set up its import profile again; the filesystem ID may have changed. ## Eject one card or all cards Choose an individual camera or emulator card for the usual one-click action. **Eject All Cards** acts on recognized card disks, not on every external volume. A disk with multiple partitions is ejected as a whole. The bulk action refuses a disk it cannot identify safely or one that shares an active import operation. Ordinary SSDs and other drives appear in **Other External Volumes** with **Eject** and **Clean & Eject** choices. By default, Easy Eject asks for confirmation before ejecting an unrecognized drive. You can change that in [Settings](https://easyeject.com/help/settings-and-shortcuts), but verify the disk and its other partitions first. ## When ejection does not finish Close Lightroom, Finder windows and other apps using the volume. Finish transfers and retry. Easy Eject does not force an unmount. Its active import source and destination are protected from normal ejection. See [Troubleshooting](https://easyeject.com/help/troubleshooting) for the issue indicator and recovery steps. --- Source: https://easyeject.com/help/clean-and-eject # Clean Mac junk files before ejecting macOS can add hidden metadata to removable storage. On emulator cards, `._` AppleDouble sidecars can look like duplicate or broken games. Some cameras and other devices also dislike this clutter. Easy Eject can clean a card before ejecting it; plain eject remains available without cleaning. ## What Clean & Eject removes The cleanup scans the selected card for regular files named `.DS_Store` or `.apdisk`, and regular files whose names begin with `._`. It tries to remove a `__MACOSX` folder only when it is empty. It skips `.Trashes`, `.Spotlight-V100`, `.fseventsd`, and `.TemporaryItems`. It does not intentionally remove ordinary photos, recordings, ROMs, or files inside a nonempty `__MACOSX` folder. Cleanup permanently removes the matching hidden files; it does not move them to Trash. Finish all copying and close apps writing to the card before cleaning. Keep a backup of important media. **Clean & Eject** is optional and off by default. ## Turn on automatic cleanup for card buttons 1. Open **Easy Eject → Settings**. 2. Turn on **Clean Cards Before Ejecting** and read the confirmation. 3. In the menu, choose an identified camera or emulator card, or use the global eject shortcut. Those card actions now clean before ejecting. For an ordinary drive under **Other External Volumes**, choose **Clean & Eject** explicitly. Check the drive name and partitions first; cleanup recursively scans that selected volume. ## App Store card permission The App Store version needs a whole-card folder grant before cleaning. Choose **Authorize a Card…**, select the card itself under **Locations**—for example, **Untitled**, rather than `DCIM`—and click **Authorize**. Authorization only grants access; it does not turn cleanup on. Formatting can require authorization again. The website version has no Easy Eject per-card authorization step, although macOS may ask it for drive access. See [Permissions and versions](https://easyeject.com/help/permissions-and-versions). If inspection or deletion fails, Easy Eject stops ejection and shows an issue. It does not force the disk to unmount after a failed cleanup. Keep the card connected, review the issue and retry only when access is fixed. See [Troubleshooting](https://easyeject.com/help/troubleshooting). --- Source: https://easyeject.com/help/air-unit-and-camera-imports # Camera and device media imports Easy Eject copies and verifies media from cameras, memory cards, action cameras and FPV devices that appear as mounted storage in Finder. You choose the device and destination once, then decide whether future connections should start an import automatically. **Videos only**, **Include camera previews** and **Clean folder layout** are available in the website version from **1.6.0**. App Store **1.1** also includes these controls and the **Device Media Imports…** window. Check your installed version before following these steps. ## Set defaults once Website **1.7.6** includes **Import defaults…** in this window and Settings. Choose media selection, previews, clean layout, automatic import, the eject prompt and optional removal once. New cards follow the defaults until you choose **Use custom settings**. Older profiles retain their saved custom options. Videos only is selected out of the box; permanent deletion and Trash recovery start off and require confirmation. [Learn about defaults](https://easyeject.com/help/settings-and-shortcuts#import-defaults-for-new-cards). ## Set up one device 1. Connect the device and open **Device Media Imports…** from the Easy Eject menu. 2. Under **Add an import device**, select the connected volume and click **Set up import…**. If several cards share a Finder name, connect only the one you want to enroll. 3. In **Step 1 of 2**, select the recording folder, such as `DCIM` or `VIDEO`. For formats that depend on a complete folder tree, select the whole card and use **All media and sidecars**. See [camera compatibility](https://easyeject.com/help/camera-media-compatibility) before narrowing the source. 4. In **Step 2 of 2**, choose a destination on another physical disk, such as your Mac or an archive drive. Copies go into a `YYYY-MM-DD` folder there. 5. Give the profile a recognizable name, choose **All media and sidecars** or **Videos only**, choose **Include camera previews**, review **Clean folder layout**, and click **Save profile**. Saving does not start an import. Click **Import now** for the first run. Review the destination and open a sample clip in your usual editor before enabling **Import automatically when connected**. Keep the Mac awake and both disks connected until the run finishes. ## Choose what to import **All media and sidecars** copies the selected folder's visible regular files, including photos, video, companion files and unfamiliar files. Leave **Include camera previews** on when you want those optional files in the saved copy too. **Videos only** selects recognized video formats and their supported companions. For recognized camera packages, it also copies the complete support tree, which may include thumbnail pictures, audio, XML and other support files. Ordinary photos outside those packages are left for your photo app. Photos, photo sidecars and unrecognized files are retained on the device, even when support files were copied. The same selection applies to optional device Trash recovery. Select the complete recording package or whole card. A source narrowed to a `CLIP` or `STREAM` subfolder can omit dependencies; ambiguous or multi-camera structures need **All media and sidecars**. Easy Eject stops before copying when it detects an incomplete or unsupported package selection. If Lightroom handles your photos, follow [Videos first, then Lightroom](https://easyeject.com/help/video-imports-with-lightroom). Copy-only imports leave videos on the card too; optional permanent deletion is what removes eligible imported videos from Lightroom's later card import. ## Choose whether to include camera previews **Include camera previews** is independent of **All media and sidecars** or **Videos only**. It starts on for new and existing profiles. Turn it off to omit recognized optional `.LRV`, `.LRF` and `.THM` files and previews in recognized `Proxy` or `Proxies` folders from the destination. Required files within a complete structured recording package stay included so the package remains usable. It is not a general filter for metadata, telemetry or unfamiliar files. Skipped previews stay on the device, including in its Trash. They are not verified saved copies, so enabling deletion or Trash recovery does not remove them. If you delete imported originals, leftover previews or the camera's recording database may need cleanup through the camera's own controls after backup. Some Studio, camera-playback or editing features use previews. Keep the option on for the most complete workflow, or turn it off when you want fewer destination files and have checked your editor. See the [camera-specific guidance](https://easyeject.com/help/camera-media-compatibility#optional-camera-previews). ## Choose the folder layout **Clean folder layout** starts on for new profiles. Existing profiles keep their original layout until you turn it on. For ordinary media, it removes camera-created folder layers such as `Camera01` from the main media list. It keeps the original filenames and selected companions together. When names would collide, groups go into **Additional media** rather than overwriting or independently renaming related clips. Unfamiliar files and recordings that need their folder tree are preserved under **Camera originals**. The recognized Insta360 index, `fileinfo_list.list`, is backed up in a hidden **`.easy-eject-metadata`** folder inside the date folder and retained on the device. Other unfamiliar files keep their source structure under **Camera originals** in an all-media import. In Finder, press **Command-Shift-period** to show hidden files. Clean layout changes where files are copied; it does not transcode, stitch or strip metadata from the media itself. Turn clean layout off to preserve ordinary source folders too. Structured and unfamiliar content still keeps its tree under **Camera originals**. Regardless of layout, choose the whole card when the recording format depends on files outside the usual media directory. No importer can copy dependencies that are outside the source you selected. ## How the device is recognized The profile uses the card's filesystem volume ID, not its name or a camera folder alone. A saved device can reappear as **Untitled 2** and still match. Formatting can change the ID and invalidate App Store folder grants; set up the newly formatted card again. Connect indistinguishable cloned cards one at a time. ## Change the destination or finish an import Use **Change destination…** to select another saved-copy folder and **Change media folder…** to select or authorize the source again. Earlier App Store builds call the source action **Authorize media folder again…**. The destination must be on a different physical disk and have enough free space. Originals stay by default. Automatic import and **Ask to eject after import** start off unless you change the new-device defaults. Permanent deletion and Trash recovery require confirmation in custom card settings or the shared defaults a card follows. In website **1.7.0**, the eject option opens a native dialog with **Keep Connected** as the default. Choose it to continue in Lightroom. A camera with multiple mounted storage sources gets a grouped confirmation; another source may still need importing. See [Import safety and options](https://easyeject.com/help/import-safety-and-options) before enabling removal or eject. PTP/MTP-only connections and devices visible only in Image Capture or Photos are not supported by this mounted-storage importer. Use a suitable card reader, a supported USB storage mode, or the manufacturer's transfer app. Check the [compatibility guide](https://easyeject.com/help/camera-media-compatibility) for recording-format limitations. --- Source: https://easyeject.com/help/insta360-quick-share # Insta360 Luna Quick Share **Availability:** Website **1.7.8 local preview**, installed on Ryan's Mac. The public Website download remains **1.7.6**. Quick Share is not in the Mac App Store edition. The [GitHub source](https://github.com/rsmith4321/Ejector) includes the preview implementation. A real card import and visual review of known I-Log footage remain to be checked. Quick Share makes compressed MP4 copies for convenient sharing. It reads the verified originals saved by a completed import and puts the new files in **Sharing Copies** inside that import's dated folder. Full-quality imported originals remain intact. The original import's card-retention or deletion settings still apply separately. ## Set up a device LUT 1. Open **Device Media Imports…**, then **Edit** your Insta360 Luna device. 2. Under **Instant LUT · Quick Share**, enable **Offer Quick Share with the Insta360 Luna LUT**. 3. Choose your preferred **1080p** or **4K** size. 4. Check that **Official Luna Rec.709 LUT ready** appears. If needed, use **Choose Luna LUT…** to install `Luna_I-Log_to_Rec709_BT1886_s33_v2.cube` from Insta360's official Luna LUT download. 5. Save the profile. Enabling this option offers a manual action. **Importing does not make sharing copies automatically.** It remains independent of shared import defaults. This preview uses FFmpeg and FFprobe already installed on the Mac; it does not bundle those tools or the manufacturer's LUT. ## Make copies after importing With **Ask to eject after import** enabled, the completion dialog adds **Quick Share…** beside **Keep Connected** and **Eject Now**. For a camera with several mounted storage sources, the same choice appears beside **Eject Camera**. 1. Choose **Quick Share…**. 2. Select **1080p** for smaller files or **4K** for more detail. 3. Enable **Apply Insta360 Luna I-Log LUT** only for footage recorded in **I-Log**. Turn it off for normal-color clips. The choice applies to all supported clips in this batch. 4. Choose **Make Quick Share Copies**. Cancel leaves the import alone. 5. When copies finish, the eject dialog offers a fresh choice. Quick Share never ejects the card automatically. You can also use **Quick Share…** under **Completed imports · Quick Share** on Device Media Imports. The last 20 completed batches remain available after card ejection and app restart. Connect their destination drive; the source card is not required. Enabling the device's LUT option after completion also makes its saved batches available. Imports completed before this preview recorded their manifests are not reconstructed by scanning old folders. ## Size and color 1080p targets about **60 MB per minute** and 4K about **180 MB per minute**, with H.264 video, AAC audio and up to 30 fps. Actual size varies. Landscape and portrait framing are retained; smaller clips are not enlarged. These are compressed sharing copies for casual viewing, not grading masters. This preview supports independent **Luna Ultra and Luna Pro master MP4s** with the embedded camera identity. It does not stitch 360 recordings or convert HDR/Dolby Vision. It cannot reliably identify I-Log from ordinary video color tags, which is why you choose whether to apply the LUT every time. Existing sharing copies are preserved. A repeat request can reuse a matching verified copy; a different size or color choice creates a separate copy. Changed saved originals or unavailable destination storage stop the export. **Stop Quick Share** cancels the current export safely while retaining originals and completed copies. Resolve the reported issue and retry from the completed import. --- Source: https://easyeject.com/help/fpv-audio-recorder # FPV audio recorder project The [FPV Audio Recorder project](https://rsmith4321.github.io/fpv-audio-recorder/) is building a small, battery-free recorder for a quadcopter using a Seeed Studio XIAO ESP32S3 Sense, its microphone, and a microSD card. The camera has been removed to save weight. The planned firmware records while the flight controller reports that the quad is armed. **Status:** A local Easy Eject website-edition preview has flashed the recorder, displayed chip temperature, and imported a WAV over USB while leaving the original on microSD. The flight-controller wiring and arm/disarm behavior have not been tested. Recorder support is not in the current public Easy Eject download. ## Planned Easy Eject flow When a recognized recorder is attached by USB, Easy Eject will offer audio import. It will show firmware setup only when the board is unprogrammed or its installed version is older than the project build on GitHub. The setup action will identify the board and ask before rewriting firmware. The XIAO currently presents a USB serial connection, not a mounted SD card in Finder. Easy Eject transfers WAV files through the recorder firmware, so its standard mounted-card import profile does not apply. You can also remove the microSD card and use a card reader with the normal card importer. For this light build, the four FC wires are soldered to the inward face of the main XIAO's plated edge pads. The low-profile joints sit protected between the XIAO and Sense boards, with the wires exiting sideways. Confirm the connector seats fully and no joint touches a component before placing a small VHB patch in a separate flat part of the gap. The microphone opening remains exposed beside the microSD slot. See the project page for the final assembly photos and wiring details. Imported recordings stay on the recorder unless you delete them separately. The recorder's live chip temperature is a diagnostic reading; provide airflow when the powered quad is stationary. See the [project page](https://rsmith4321.github.io/fpv-audio-recorder/) for current build and test status before wiring or flying it. --- Source: https://easyeject.com/help/video-imports-with-lightroom # Videos first, then Lightroom If you prefer Lightroom for photos and a separate video editor for footage, **Videos only** lets Easy Eject handle the video transfer. Your photos stay on the card for your normal Lightroom import. The media options require website **1.6.0 or later**; the current dialog flow described here is in website **1.7.0**. App Store **1.1** also includes the media options and dialog-based eject choices. ## Set up the profile 1. Open **Device Media Imports…** and create or edit the card's profile. 2. Select the recording folder and a destination on a different physical disk. Choose **Videos only**. **Include camera previews** is a separate choice: leave it on for previews and proxies, or turn it off to skip recognized optional ones. 3. Leave permanent deletion off for your first test (**Keep originals is on**). Choose **Clean folder layout** if you want ordinary clips together without camera-created folder layers. 4. Enable **Ask to eject after import** to see an eject dialog after completion. Choose **Keep Connected** to continue in Lightroom, or choose **Eject Now** when you are finished with the card. This replaces the previous automatic-eject option; existing enabled profiles now ask first. 5. Save, then run **Import now**. Open a saved clip in your video editor and check the destination before enabling automatic importing. Easy Eject selects recognized videos and supported video companions. A recognized camera package also brings its complete support tree, including any thumbnails, audio and XML it needs; ordinary photos outside that package are left for Lightroom. Photos, photo sidecars and unrecognized files stay on the device even if package support files were copied. RAW photo sequences are not treated as ordinary video clips. Incomplete or ambiguous recording structures stop with an explanation. Same-name still/movie pairs are conservatively left together for the photo workflow, including likely Live Photos. Renamed or separated pairs may not be recognized; videos-only does not identify every motion photo by its internal metadata. Keep deletion off when testing such media. ## Decide whether videos should stay on the card Copying alone leaves the videos on the device, so Lightroom may still display them in its import window. You can keep this safer copy-only workflow and deselect those clips in Lightroom. If you want eligible imported videos removed before Lightroom reads the card, enable **Permanently delete imported videos** for that profile and read the confirmation. Easy Eject verifies the saved batch before removing eligible imported files. Deletion bypasses Trash and cannot be undone. Photos and their sidecars stay; unknown files, device indexes and skipped previews stay too. Keep independent backups of valuable footage. With camera previews excluded, imported originals can be removed while their skipped previews remain on the card. Use the camera's own cleanup or formatting workflow after the photos and videos are backed up. Deleting files through any computer workflow can leave a camera's recording database out of sync. Some cameras need their own recovery command afterward. Leave deletion off if your camera or recording format requires whole-card management, and check the [camera guide](https://easyeject.com/help/camera-media-compatibility). ## Import in this order 1. Connect the card and let Easy Eject finish. Keep other importers idle during its transfer and any removal. 2. Read the result and check the saved video folder. A stopped import can leave some completed copies without clearing every video from the card. 3. Choose **Keep Connected** in the completion dialog, then open Lightroom's import window and import the remaining photos using your normal settings. If you chose **Eject Now**, unplug and reconnect the device first. Review the selection; files outside Easy Eject's source or supported video selection may still appear. 4. Wait for Lightroom to finish, then eject the card with Easy Eject or Lightroom when it offers that option. The dialog also appears when selected files already have verified copies, or no media matches the profile. **No media found** does not mean the entire card or camera is empty: photos, skipped previews, or recordings on another storage source may remain. **Keep Connected** is the default. A camera exposing multiple mounted storage sources gets a grouped confirmation listing them; finish every desired import before choosing **Eject Camera**. Failed or unreadable imports show an error instead of a completion choice. Easy Eject does not import photos into a Lightroom catalog, set Lightroom preferences, or coordinate Lightroom's import queue. If Lightroom opens its import dialog too early, its General preferences include **Show Import Dialog When A Memory Card Is Detected**. You can turn that off and open Import when the video transfer finishes. [Adobe's import preferences](https://helpx.adobe.com/lightroom-classic/desktop/import-photos/file-import-formats-settings.html) Lightroom Classic supports many common video formats as well as photos, which is why retained clips may appear alongside pictures. Its import window lets you choose what to include. [Adobe's supported video formats](https://helpx.adobe.com/lightroom-classic/desktop/kb/video-support-lightroom.html) · [Adobe's photo import guide](https://www.adobe.com/learn/lightroom-classic/web/import-photos) --- Source: https://easyeject.com/help/camera-media-compatibility # Camera compatibility and media files A clean import is useful only if your editor can still use the footage. Some cameras save a self-contained movie; others rely on several files, original names or a complete recording folder. Easy Eject keeps original bytes and names, and preserves structure where flattening would be unsafe. It does not convert formats, stitch 360 footage or join split recordings. This guide combines manufacturer documentation with Easy Eject's import behavior. It is **not a list of camera models physically tested with Easy Eject**. Recording mode, firmware and connection type can change the files a device produces. Test a copy-only import in your actual editor before enabling automatic deletion. The new media-selection, camera-preview and clean-layout controls require website **1.6.0 or later**. ## Check the connection first The camera or card must appear as a mounted volume in Finder. Use a card reader or a supported USB storage mode. A camera visible only through Photos, Image Capture, PTP or MTP needs another transfer method. Choose `DCIM` or the recording folder for ordinary files. Choose the **whole card**, **All media and sidecars**, and keep deletion off when a format uses a database or directory tree. This copies supported source files; it is not a disk image or a replacement for the manufacturer's archive tool. If you are unsure, preserve the original layout and card until the editing workflow is verified. ## Optional camera previews **Include camera previews** starts on for new and existing profiles and works independently of **Videos only**. Turn it off to skip recognized optional LRV, LRF and THM files and previews in recognized `Proxy` or `Proxies` folders. Required files inside a complete structured recording package remain included; turning this option off does not flatten or strip a recording package. Preview requirements vary by camera and editor. Some Studio and camera-playback features use them. You can choose a cleaner destination when your workflow does not need the optional previews, but do not assume every LRV or proxy is disposable. Skipped previews are retained on the device, even when imported originals are deleted or device Trash recovery is enabled. Clean up leftover previews through the camera's supported workflow after backing up the originals. The option does not classify telemetry, blackbox logs, captions or all unfamiliar metadata as preview clutter. Their handling still follows the selected media and compatibility rules. ## Insta360 Luna and ordinary camera movies Insta360's Luna Ultra instructions tell users to copy photo and video files from `DCIM/Camera01`. Studio also accepts local MP4 and MOV files. That supports bringing the original media into a simpler destination folder without retaining `Camera01` as a visible layer. It does not establish that every device-side file is disposable. [Luna computer transfer](https://onlinemanual.insta360.com/lunaultra/en-us/operation-tutorials/connection/pc) · [Studio local-file import](https://onlinemanual.insta360.com/studio/en-us/operation-guide/file-management/creative-import) An index such as `fileinfo_list.list` is not listed as an input in those instructions. Easy Eject backs it up in hidden **`.easy-eject-metadata`** and retains it on the device. This keeps it out of the main media list without assuming it has no purpose. Keep all parts of long recordings and their original names. Luna Ultra can split long recordings into segments that Studio joins; copying one segment is not the whole recording. [Luna recording storage](https://onlinemanual.insta360.com/lunaultra/en-us/operation-tutorials/sdcard-file-storage/sdcard) ## Insta360 360 and multi-lens recordings Some Insta360 recordings have paired originals, such as files containing `_00_` and `_01_`. Keep both together with their original names. Insta360 also recommends retaining corresponding LRV files. Leave **Include camera previews** on to retain optional LRV previews in the destination, or turn it off after checking which Studio features your workflow needs. Both original lens files remain essential; do not rename a single part or assume one large file is the complete clip. Open the copied set in Studio to check it. [ONE R import instructions](https://onlinemanual.insta360.com/oner/en-us/studio/import/importfootage) · [Studio media-import troubleshooting](https://onlinemanual.insta360.com/studio/en-us/troubleshooting/file-import-issue/media-import-issue) Insta360 Pro 2 and Titan are different: their workflow uses the complete recording folder, including lens originals, project information, gyro data and preview files. Use **All media and sidecars**, select the whole required source, preserve the folder structure and keep deletion off. Do not move only the obvious MP4 files into a flat folder. [Pro 2 stitching workflow](https://onlinemanual.insta360.com/pro2/en-us/video/postproduction/1) · [Titan stitching workflow](https://onlinemanual.insta360.com/titan/en-us/video/postproduction/1) ## GoPro and split recordings GoPro may divide one recording into chapters. Keep every chapter and its original name; a collection of files can be one continuous recording. Easy Eject copies them without combining or remuxing them. GoPro's own chapter tools pay special attention to metadata when joining footage, so use a suitable editor or vendor workflow for that step. [GoPro Labs: chapters](https://gopro.github.io/labs/control/chapters/) Low-resolution proxies and thumbnails can be useful companions. **Include camera previews** lets you retain or skip recognized optional ones independently of your media selection. Keep them when needed for your workflow, especially while testing a new model or recording mode. ## DJI cameras, drones and FPV devices DJI devices can record ordinary video along with proxies and caption files. LRF proxies support functions such as playback on some DJI cameras; DJI warns that removing a corresponding LRF can prevent on-camera video playback. SRT captions may carry recording data such as location, time and camera information. The camera-preview option can exclude recognized optional LRF files from the destination while retaining them on the source. SRT recording data is a different kind of companion and is not excluded as preview clutter. [DJI: LRF files](https://repair.dji.com/help/content?customId=01700006938&lang=en&paperDocType=ARTICLE&re=US&spaceId=17) · [DJI video-caption documentation](https://developer.dji.com/api-reference/ios-api/Components/Camera/DJICamera.html) A DJI O4 air unit is one example of a device import profile; Easy Eject's importer is also intended for suitable mounted cameras and cards. Connection support does not guarantee that every recording mode can be flattened. Retain the source while checking your editor, telemetry and stabilization workflow. ## Sony, AVCHD and professional camera structures Sony formats may use trees such as `AVCHD/BDMV`, `M4ROOT`, `XDROOT`, `BPAV` or `CINEROOT`. Catalyst's copy workflow preserves related metadata and proxies and understands spanned clips. Use **All media and sidecars** with the whole card, preserve the structure and keep deletion off when those relationships matter. Easy Eject may place the retained tree under **Camera originals**; point the editing application at the appropriate copied root. [Sony supported formats and folders](https://helpguide.sony.net/di-app/cp/v1/en/Content/Supported_devices.htm) · [Catalyst clip copying](https://helpguide.sony.net/di-app/cp/v1/en/Content/Copying_clips.htm) A playable individual MP4 or MTS is not proof that camera management information is unnecessary. Deletion through a computer can leave a camera's database inconsistent and may require an in-camera recovery step. Keep deletion off if your camera's instructions require their own management workflow. Panasonic P2 requires **CONTENTS** and **LASTCLIP.TXT** together and warns against individual file transfers or deletion. Panasonic also warns that partially deleting AVCHD/MOV/MP4 management information can affect recognition or recording. Copy the complete required structure and use the manufacturer's tools for card management. [Panasonic P2 card handling](https://eww.pass.panasonic.co.jp/pro-av/support/content/faq/EN/p2card_handling_en.htm) · [Panasonic recording structure](https://eww.pavc.panasonic.co.jp/hdw/oi/AG-CX20/html/AG-CX20_CX18_DVQP3341_eng/0019.html) Canon XF workflows likewise depend on their original folder structure, and Canon explicitly warns against deleting clips directly through a computer. Use a complete structured copy and the supported Canon workflow. [Canon XF file precautions](https://asia.canon/en/support/8202151400) · [Canon XF Utility manual](https://gdlp01.c-wss.com/gds/5/0300003875/04/xf-utility-131-w-im-en.pdf) ## Photos, motion photos and unfamiliar files RAW photos, JPEG/HEIF pictures and photo sidecars belong to the photo workflow. A Live Photo can include a still image and a paired movie; a movie extension alone does not mean it should be separated from the photo. Easy Eject conservatively leaves a movie with a same-name photo for the photo workflow. It does not identify every pair by internal metadata: renamed or separated pairs may not be recognized. Keep deletion off while checking such media. [Apple: Live Photo resources](https://developer.apple.com/videos/play/wwdc2016/501/) Videos-only selects supported media and recognized recording packages; it is not a promise to identify every recording a device can make. A complete package may contain thumbnail pictures, audio, XML and other support files, which are copied together. Ordinary photos outside the package are left for your photo app. Unrecognized files and photo files remain on the device after optional video deletion. For unfamiliar cameras, RAW image sequences, audio recorders or specialized professional formats, use **All media and sidecars** with the original structure and keep the card until the saved set is verified in its intended application. ## When Easy Eject asks for a complete card copy Videos-only can copy recognized complete packages, including their support files, while retaining ordinary photos elsewhere on the card. If the selected folder is too narrow, such as `CLIP` or `STREAM`, choose the complete recording package or whole card. If the package is ambiguous or uses multiple cameras, choose **All media and sidecars**. The importer stops before copying when it detects those unsupported selections. Clean layout preserves detected structures instead of flattening them; turning it off preserves ordinary camera folders too. For Panasonic P2, Canon XF and other formats whose manufacturers require their own file-management tools, our recommendation is to keep originals and follow that vendor workflow. This is compatibility guidance; Easy Eject does not silently change a saved deletion setting. Detection cannot recognize every manufacturer's current and future format. Use the camera's manual when it asks for a complete folder or vendor import tool, even if Easy Eject has not shown a warning. [Set up an import](https://easyeject.com/help/air-unit-and-camera-imports) · [Import safety](https://easyeject.com/help/import-safety-and-options) --- Source: https://easyeject.com/help/import-safety-and-options # Import safety, originals and Trash The new selection and layout options described here require website version **1.6.0 or later**. App Store **1.1** also includes these options. Keep deletion off while first checking your workflow. ## What happens during an import Easy Eject scans the selected source, plans the chosen files and copies them into a dated destination folder. It compares each saved file with a SHA-256 hash of the source and attempts to flush verified copies to storage. It checks source and destination volume identities during the run. Existing copies are reused only when their contents match; conflicting media is kept separate without overwriting it. **All media and sidecars** includes visible regular files from the source, including unfamiliar files. **Videos only** selects recognized videos and supported companions. The independent **Include camera previews** setting starts on for new and existing profiles. Turn it off to skip recognized optional previews in either media mode. Recognized recording packages retain their required support tree, even when it contains thumbnails, audio, XML or unfamiliar support files. Ordinary photos outside packages are not selected, and photos, photo sidecars and unrecognized files remain on the device after optional deletion. Incomplete or ambiguous package selections stop before copying. See [camera compatibility](https://easyeject.com/help/camera-media-compatibility). An error or cancellation can leave completed destination copies while remaining source files stay on the device. Partial copies are removed when an operation stops. Read the result in the import window or log rather than assuming that every file was copied or removed. ## Originals stay by default Keeping originals is the default (**Keep originals is on** in the profile editor). Automatic import, permanent deletion, device Trash recovery and post-import eject all start off for new profiles. Changing the selection, preview choice or layout does not by itself authorize deletion. Use copy-only import for the first run with a new device or recording mode. Open the saved media in the intended editor, including long clips, 360 recordings and their companions. A checksum verifies copied bytes; it does not prove that an editor supports the format or that every required file was inside the selected source. ## Permanent deletion of imported files The profile editor offers **Permanently delete imported videos** in videos-only mode or **Permanently delete imported originals** for all media. It requires a separate confirmation. Eligible source files are removed directly, without Trash, after the saved batch passes verification. This cannot be undone through Easy Eject. Deletion is limited to recognized imported media and eligible companions. Unrecognized files and device indexes are retained, even if they were copied. Previews skipped with **Include camera previews** off are not copied or verified, so they are not removed from the device or its Trash. Videos-only mode leaves photos and their sidecars, including those in the device's Trash. If a source or destination changes or a required safety check fails, the operation stops; inspect the result before retrying. Do not record onto, rename or rearrange files on the card while importing. Keep valuable footage backed up independently. Some cameras maintain a database that can need recovery after computer-side deletion; check the manufacturer's workflow and leave deletion off when a complete recording structure must remain intact. ## Optional previews and source cleanup With **Include camera previews** off, Easy Eject skips recognized optional LRV, LRF and THM files and files in recognized preview folders. Required files inside complete structured recording packages stay included. Telemetry, captions, blackbox logs and unknown files are not discarded merely because they are small or are not playable movies. Skipped previews remain on the device after eligible imported originals are deleted. This can leave previews without their original clip; the camera's database may also need recovery or cleanup. Use the camera's supported cleanup or formatting workflow after all wanted media is backed up. Some Studio or on-camera preview features need these files, so choose the setting for your actual editor and device. ## Clean folders preserve media and dependencies Clean layout preserves original media bytes and names. Ordinary media is brought together; collisions use **Additional media** groups, while structured or unfamiliar content keeps its relative folders under **Camera originals**. The recognized Insta360 `fileinfo_list.list` index is backed up under hidden **`.easy-eject-metadata`** and remains on the device. The [import guide](https://easyeject.com/help/air-unit-and-camera-imports#choose-the-folder-layout) explains when to preserve the original layout instead. ## Device Trash recovery **Recover and clear this device's Trash** is separate and opt-in. Selected files from that device's current-user Trash are copied into **Recovered Device Trash**, verified, then eligible originals are removed from that Trash. It does not act on other drives' Trash. The App Store version needs a whole-card grant in addition to import-folder and destination grants. In **Videos only** mode, recovery uses the same video-and-package selection as the import. Removal is limited to eligible videos and supported companions; photos, photo sidecars and unrecognized items stay in Trash, including package support files that were copied. The camera-preview choice applies here too: skipped optional previews stay in Trash. Recovery does not authorize clearing the device's entire Trash. ## Ask to eject after import {#eject-after-a-verified-import} In website **1.7.0**, **Ask to eject after import** shows a native dialog. **Keep Connected** is the default; choose **Eject Now** when you have finished all desired imports. The built-in default for this option is off; new profiles can inherit your chosen [import defaults](https://easyeject.com/help/settings-and-shortcuts#import-defaults-for-new-cards). A successful import shows **Import complete**. An empty selection shows **No media found**, including cards with only photos when Videos only is selected, or only skipped previews. Already-imported selections are verified before offering the choice. No-media describes the selected source and options, not the whole camera. For a camera exposing multiple mounted storage sources, such as Internal and SD Card, the grouped dialog lists the sources and offers **Eject Camera**. They may need separate import profiles. Finish importing every source before accepting the grouped eject. Easy Eject checks the exact storage group and identities before each sequential unmount; a changed group or failed unmount stops the operation. The dialog does not depend on Notification Center or Focus. Eject remains available in the menu and import window. Before acting, Easy Eject revalidates the source volume, physical disk and connection; disconnecting, reimporting or restarting invalidates old completion actions. Active imports and eject operations are protected. Failed imports, unreadable cards and unavailable folders remain errors. If the selected folder is absent, a no-media result is allowed only when a readable card scan confirms there are no other ordinary files. Public App Store **1.1** includes these updated dialogs. Website 1.6.2 used notification actions; upgrade to 1.7.0 for the current dialog flow. ## Before clearing or formatting a card - Keep the Mac awake and the destination connected until the import finishes. - Review the result and open saved files in the editor you intend to use. - Check for recordings outside the selected source folder. - Keep an independent backup of important media. - Finish Lightroom and other transfers before ejecting or formatting. --- Source: https://easyeject.com/help/permissions-and-versions # Permissions and the two versions Easy Eject is available as a [signed, notarized website download](https://easyeject.com/#website-version) and on the [Mac App Store](https://apps.apple.com/us/app/easy-eject/id6767951388). Both provide ejection, optional cleaning and media imports, with different permission and update paths. As of October 5, 2026, the public releases are **website 1.7.6** and **App Store 1.1**. Store 1.1 includes videos-only imports, shared import defaults, camera-preview and clean-layout options, and updated dialogs. Manual [Insta360 Quick Share](https://easyeject.com/help/insta360-quick-share) is a local Website 1.7.8 preview and is not in either public download. | Action | Website version | App Store version | | --- | --- | --- | | Plain eject | No Easy Eject folder grant | No folder grant | | Recognize card hardware | Uses available disk information | Uses available disk information | | Inspect camera or emulator folders | macOS may request removable-drive access | Authorize the whole card | | Clean hidden Mac files | macOS may request drive access | Authorize the whole card | | Import media | Select a source media folder and a destination | Grant the media folder and destination through the picker | | Recover device Trash | Optional profile setting | Optional setting plus whole-card grant | | Updates | Automatic checks for signed GitHub updates; approval before installation | App Store; automatic when enabled in its settings | The App Store edition runs inside the App Sandbox. It uses user-selected folder access and saved permissions. **Full Disk Access does not bypass the sandbox or replace Authorize a Card.** Full Disk Access and Accessibility are not required for the Store edition. Apple describes these as [separate access restrictions](https://developer.apple.com/forums/thread/124895). The website edition has no Easy Eject **Authorize a Card** requirement for detection or cleaning, including after camera formatting, but macOS itself may ask for drive access or require a renewed system permission. It is the more convenient choice if you regularly swap or format cards. ## CFexpress detection and card access A reader that explicitly reports CFexpress hardware can be identified from disk information without opening its folders. Some generic PCI/NVMe readers do not report that identity, so Easy Eject needs to inspect camera folders such as `DCIM`. **The Store edition needs authorization for that folder inspection**, even if you give the app Full Disk Access. Without that grant, the card may appear under **Other External Volumes**. You can still use plain **Eject** there without folder authorization. Authorize the whole card to allow folder-based recognition and optional cleanup. ## Authorize a whole card in the App Store edition 1. In the menu or Settings, choose **Authorize a Card…**. 2. In the folder picker, find the card under **Locations**. Select the card itself, for example **Untitled**, rather than `DCIM` or a folder inside it. 3. Click **Authorize**. This remembers access for this filesystem volume. Then separately enable **Clean Cards Before Ejecting** if you want card-button cleanup. Authorization does not start an import or enable deletion. **You do not normally need to authorize the same card on every connection.** Access is remembered across reconnects and app restarts. A new card, formatting that changes its volume identity, or an invalid saved permission can require authorization again. **Forget** in Settings removes a saved card permission. ## Source and destination grants for imports The import setup asks for a *source folder* such as `DCIM` or `VIDEO` and a *destination folder* on a different physical disk. In website version 1.6.0, select the whole card for recording formats that depend on a complete folder tree, using **All media and sidecars** and keeping deletion off. These are separate selections from whole-card authorization. Use **Change media folder…** or **Change destination…** if source or destination access fails. Earlier App Store builds call the source action **Authorize media folder again…**. Whole-card authorization is additionally needed for optional device Trash recovery, because `.Trashes` sits outside the media folder. ## Downloads and updates The website download button downloads the DMG directly from **GitHub Releases**. From **1.7.0**, Easy Eject automatically checks for signed updates and asks before installation. You can also choose **Check for Updates…**, or turn automatic checks off in Settings. The updater waits for active work and open dialogs before restarting. **Website 1.6.2 and earlier need one manual upgrade** to get the updater: download the DMG, quit Easy Eject when idle, and replace it in Applications. Later updates can be installed through Easy Eject. The Store edition receives updates through the **Mac App Store**. Automatic installation follows your App Store update settings and Apple's release availability. ## Switching editions Quit the current edition before opening the other. The two bundle IDs keep their own settings, profiles and permissions; review the profile in the edition you choose. Do not run two automatic importers on the same device. A formatted card may need a new import profile in either edition. [Get started](https://easyeject.com/help/getting-started) with plain eject if you do not need imports. --- Source: https://easyeject.com/help/settings-and-shortcuts # Settings and keyboard shortcut Open **Settings…** from the Easy Eject menu. Most options are off until you choose them. The app's menu is also available from the **Eject menu** button in the imports window. ## General - **Launch at Login** starts Easy Eject when you sign in. macOS may require approval in **Login Items**. - **Clean Cards Before Ejecting** removes matching hidden Mac metadata before the menu's card buttons and global card shortcut eject a card. It is off by default and asks for confirmation when enabled. See [Clean & Eject](https://easyeject.com/help/clean-and-eject). - **Confirm Before Ejecting SSDs** asks before ejecting drives that are not recognized as cards. It starts on. Read the prompt carefully because physical eject also unmounts other partitions. - **Show Eject Notifications** controls system notifications. If macOS has denied notifications, adjust Easy Eject's notification setting in System Settings. Website 1.7.0 uses a native dialog for Ask to eject after import, regardless of notification settings. Keep Connected is its default. ## Import defaults for new cards In website **1.7.6**, choose **Import defaults…** in Device Media Imports, or use **Defaults for new import devices** in Settings. Choose: - Videos only (the initial default) or All media and sidecars. - Whether to include optional camera previews. - Clean folder layout for ordinary clips and companions. - Automatic importing on future connections. - The post-import eject prompt. - Permanent deletion of verified imported originals. - Verified recovery of media from the device Trash. New cards use **Use defaults** and follow these settings on their next import. Their inherited options are greyed out; choose **Use custom settings** to edit options for that card. Older profiles retain their saved settings as custom settings. An import already running keeps the options it started with. Permanent deletion and Trash recovery start off. Enabling either requires confirmation in shared defaults or custom card settings. Shared removal settings apply to all cards using defaults, including future cards. Changing Videos only to All media switches both removal settings off for review. Store Trash recovery also needs whole-card authorization. Saving a profile does not start an import. Done, Cancel and Save stay visible below scrolling settings, and folder selectors keep their navigation sidebar readable. ## Website app updates Website **1.7.0** automatically checks GitHub for signed updates and asks before installation. Use **Automatically check for updates** in Settings to turn checking on or off, or choose **Check for Updates…**. Installation waits for imports, ejection and open dialogs to finish before restarting. There are no silent installations or system-profile uploads. The Store edition uses Apple's updater. Public Store **1.1** includes shared defaults. ## Global eject shortcut Enable **Global Eject Shortcut** and choose a letter. The shortcut is **Control–Option–Command** plus that letter; **E** is the default. It invokes **Eject All Cards** for recognized camera and emulator cards. If cleanup is enabled, the shortcut also cleans those cards. It uses a registered macOS hotkey and does not need Accessibility access. A conflicting shortcut can prevent registration. Settings shows whether the shortcut is active; choose another letter or use the menu if it says unavailable. Check every connected card before invoking the all-card shortcut. ## Debug logs and issues **Enable Debug Logging** adds drive-identification detail to the in-app debug window. The separate import log records import results and may contain local filenames and paths. The **Needs attention** icon points to an issue in the imports window. **Dismiss** clears the attention indicator, but it does not retry, change a profile, or repair a failed import. The last issue remains readable until another operation replaces it. See [Troubleshooting](https://easyeject.com/help/troubleshooting). --- Source: https://easyeject.com/help/troubleshooting # Troubleshooting cards, imports and ejection ## My CFexpress card appears under Other External Volumes Some generic PCI/NVMe readers do not identify themselves as CFexpress hardware. Easy Eject may need to inspect a `DCIM` or other camera folder to classify the volume. In the App Store edition, [authorize the whole card](https://easyeject.com/help/permissions-and-versions) for that inspection. You can choose **Eject** under **Other External Volumes** without this permission. In the website edition, use **Refresh List** after connecting a card or allowing macOS drive access. ## I see Untitled 2, or the wrong import device The Finder name can change when another card with the same name is connected. A saved import profile matches a filesystem volume ID rather than the displayed name. During setup, connect only the device you intend to enroll and give its profile a recognizable name. After formatting, the ID can change; set up a new profile. If you have two block-level clones with the same volume ID, keep only one connected for automatic importing until the app can distinguish them. ## The card is busy or won't eject Finish Lightroom, Finder, and any other copy or write operation. Close apps with files open on the card, then retry. Easy Eject does not force an unmount. If cleanup failed, fix the access or file issue and retry; cleanup does not silently fall back to plain eject. If a disk has several partitions, check all of them before ejecting the physical disk. An active Easy Eject import also protects its source and destination from normal eject commands. ## An import says Needs attention Open **Device Media Imports…** (called **Air Unit & Camera Imports…** in earlier versions) and read the full issue. **Dismiss** only clears the menu-bar warning; it does not retry or change a saved profile. Then check: 1. Is the original device still connected and mounted in Finder? 2. Is the chosen destination connected, writable, and on another physical disk with enough free space? 3. Did the card get reformatted, changing its volume ID? Enroll it again. 4. In the App Store edition, did the media-folder or destination permission expire? Use **Change media folder…** (called **Authorize media folder again…** in earlier Store builds) or **Change destination…**. Whole-card authorization is separate and needed for cleaning or device Trash recovery. 5. Did the Mac sleep or another app add recordings during the import? Keep it awake and rerun **Import now** after checking partial destination copies. The app checks copies before declaring completion. An interrupted import may leave finished copies at the destination and originals on the device. Avoid manually clearing the card until you have inspected the destination. ## Eject prompt did not appear {#automatic-eject-did-not-run} In website **1.7.0**, enable **Ask to eject after import** for the profile. Successful imports and scans use a native dialog, including when no media matches the options or all selected media already has verified copies. **Keep Connected** is the default. Notification permissions and Focus do not control this dialog. Eject remains available in the menu, and the import window has an **Eject Now** button for completed, still-connected devices. A camera exposing multiple storage sources gets a grouped confirmation listing them. A no-media result on Internal does not mean its SD Card is empty; set up and import that source separately if needed. Disconnecting/reconnecting, importing again, or restarting the app expires its old completion action. A busy or changed disk prevents ejection. Failed or unreadable imports remain errors. Website 1.6.2 used notification actions; upgrade to 1.7.0 for the current dialog flow. ## I need help from Ryan Use [Contact Ryan](https://www.ryansmithphotography.com/contact/) or [report an issue on GitHub](https://github.com/rsmith4321/Ejector/issues). Include the app edition and version, macOS version, reader/card model, what you clicked, and the exact error. Do not publicly post private footage, credentials, or unredacted logs containing private paths. See [Privacy, logs and support](https://easyeject.com/help/privacy-and-support). ## I still see Camera01, unfamiliar files or extra folders In website version 1.6.0 or later, enable **Clean folder layout** in the profile to bring ordinary media into the main dated folder. Existing profiles keep their earlier layout until you choose this option. It affects future imports; Easy Eject does not reorganize past destination folders. **Additional media** keeps conflicting names separate without breaking related filenames. **Camera originals** preserves unfamiliar files and folder-dependent recordings. The recognized Insta360 **fileinfo_list.list** index is backed up under hidden **.easy-eject-metadata** and retained on the device. These are deliberate safeguards, not a failed flattening step. See [camera compatibility](https://easyeject.com/help/camera-media-compatibility). ## Videos-only asks me to use the whole card Some recordings need their directory tree, project data, proxies or several related files. The importer copies the complete support tree for recognized packages. It stops before copying if the source is too narrow or the package is ambiguous. Choose the complete recording folder or whole card; for ambiguous or multi-camera structures, use **All media and sidecars**. Keep deletion off while verifying a new recording workflow. Follow the camera's documented import method if its required files span multiple cards or devices. ## Lightroom still shows videos after an import Copy-only import leaves videos on the device. Only the separate, confirmed **Permanently delete imported videos** option removes eligible imported videos after verification. Videos outside the selected source or supported selection, interrupted imports, and retained motion-photo components may still appear. Review Lightroom's selection and see [Videos first, then Lightroom](https://easyeject.com/help/video-imports-with-lightroom). ## Previews are missing from the import, or left on the device Check **Include camera previews** in the profile. When off, it skips recognized optional LRV, LRF, THM and preview-folder files. It still copies files required within a complete structured recording package. The choice is separate from **Videos only**. Skipped previews stay on the device and in its Trash, including when permanent original deletion is on; Easy Eject has not made a verified saved copy of them. If the originals were removed, use the camera's supported cleanup after backup. Turn preview inclusion on for future imports if Studio, your editor or camera-preview workflow needs those files. See [camera compatibility](https://easyeject.com/help/camera-media-compatibility#optional-camera-previews). --- Source: https://easyeject.com/help/privacy-and-support # Privacy, logs and contacting support Easy Eject works with files on your Mac and connected storage. It has no account, advertising or analytics feature. It does not upload your media. The App Store edition has no network entitlement; its local settings, bookmarks and logs live in its app sandbox. The website edition also processes media locally, but from version 1.7.0 its automatic update checker periodically contacts GitHub for release information. You can disable automatic checks in Settings; approved updates also download from GitHub. No system profile is sent. GitHub receives normal connection information such as your IP address. The import log stays on your Mac unless you choose to share it. It can include filenames and source/destination paths. Debug logging can show disk details. Review and redact that information before posting a GitHub issue or sending a support message. For a useful report, include the app edition and version, macOS version, reader/card type, and the exact visible error. Do not send original client media or passwords unless Ryan specifically needs them for an agreed support case. This help site is hosted on the same Easy Eject website infrastructure. Its local search runs in your browser; there is no help-site account. Website delivery through the hosting provider and Cloudflare uses ordinary connection information. Links to GitHub, the App Store, ShootCal or Ryan Smith Photography open those services in your browser. Read the complete [Easy Eject privacy policy](https://easyeject.com/#privacy) for both editions and the website. For support, [contact Ryan](https://www.ryansmithphotography.com/contact/) or [file a GitHub issue](https://github.com/rsmith4321/Ejector/issues).