Always copy readable files or recover missing data before attempting to repair an SD card on your Mac, because built-in tools like Disk Utility First Aid alter file-system metadata and are not undelete tools.
● macOS cannot measure an SD card's remaining flash life because most consumer cards do not expose S.M.A.R.T. data, making Activity Monitor and speed tests invalid for checking physical card health.
● Use the read-only Terminal command diskutil verifyVolume to check the logical file system if you want to verify the selected volume without intentionally running repairs that could jeopardize unstable data.
● To test a card for counterfeit capacity or obvious read/write defects on Apple silicon or Intel Macs running macOS 13 or later, run the F3XSwift write-and-read test strictly on an empty card after securing backups.
Ask AI for a summary
To check an SD card for errors on a Mac, protect any important files first, then run First Aid in Disk Utility or use diskutil verifyVolume in Terminal. These checks can find file-system and partition-structure problems, but they do not measure flash wear or guarantee that the card is physically healthy. If files are already missing, recover them before you repair or format the card.
Safest first move: Stop recording to the card. Copy readable files to another drive, or recover missing files before running a repair.
Best built-in check: Disk Utility First Aid checks and can repair formatting and directory-structure errors.
Best read-only command: diskutil verifyVolume verifies the selected volume without intentionally repairing it.
Important limitation: Most SD and microSD cards do not expose useful S.M.A.R.T. data to macOS. Activity Monitor and a speed test are not health reports.
In this article
Part 1. Can macOS Really Check SD Card Health?
macOS can check whether an SD card is detected, mounted, logically consistent, readable, and writable. It cannot normally show the card's remaining flash life. The phrase check SD card health on Mac therefore covers several different questions, and each needs a different test.
| What You Need To Know | Right Tool | What The Result Actually Proves |
| Does macOS detect the card? | Disk Utility or diskutil list external physical |
The Mac can see a storage device through the current slot, reader, cable, and port. |
| Is the file system logically consistent? | Disk Utility First Aid or diskutil verifyVolume |
The FAT32, exFAT, HFS+, or other supported file-system structures can be checked. A repair may alter metadata. |
| Is the partition map valid? | First Aid on the physical device or diskutil verifyDisk |
The partition-map layout is checked. This is not a bad-block scan. |
| Does the card have its advertised usable capacity? | F3XSwift after backup or recovery | A write-and-read test can reveal fake capacity and obvious read/write defects in the tested space. |
| Are deleted or missing files recoverable? | Recoverit for Mac | A scan can locate recoverable file records or signatures. Recovery depends on the card's condition and whether old data has been overwritten. |
| How much flash life remains? | No dependable built-in SD card test | Most consumer SD cards and readers do not expose a useful S.M.A.R.T. endurance report to macOS. |
Do not use Activity Monitor as an SD card health checker. It reports process and system activity, not the condition of flash cells. A benchmark can measure current speed, but a fast result does not prove that the card is healthy, genuine, or safe for important footage.
Part 2. Before Repair: Protect The Files First
First Aid and Terminal repair commands can change file-system metadata. That may be appropriate after the files are safe, but it is the wrong first move when photos, videos, or project files have disappeared. Use this decision rule before checking or fixing the card.
When To Copy, Recover, Or Stop DIY
| What You See | Safest Next Step |
| The card opens and all files are visible. | Copy the files to your Mac or another healthy drive before running First Aid or a write test. |
| The card opens, but files or folders are missing. | Stop using the card and scan it with recovery software before repair or formatting. |
| macOS says the disk is unreadable or asks you to initialize it. | Click Ignore, not Initialize. Recover needed files first if the device is detected. |
| The card appears in Disk Utility but will not mount. | Recover or copy important data first; then try First Aid or Mount. |
| No Mac, camera, or known-good reader detects the card, or it is cracked, burned, bent, or unusually hot. | Stop DIY attempts. Software cannot scan a device that the system cannot access; use a professional recovery lab for valuable data. |
How To Recover Missing SD Card Files With Recoverit
Recoverit for Mac is relevant when the card is detected but files were deleted, formatted, hidden by file-system damage, or lost after an interrupted transfer. It supports common photo, RAW, video, audio, document, archive, and project-file formats. Do not install the software on the SD card, and never save recovered files back to the same card.
- Connect and select the card: insert the SD or microSD card through a stable reader. Open Recoverit, choose SD Card Recovery, confirm the card by its name, capacity, and file system, and click Start Scan.

- Let the scan run: use file type, path, search, and filter options to narrow the results. If the card is unstable, preview the most valuable files as soon as they appear.

- Preview and recover: preview supported files, select what you need, click Recover, and save the results to the Mac's internal drive or another healthy external drive.

No recovery tool can guarantee every file. Success is highest when the loss was logical and the card has not been reused. If you need a broader recovery workflow, see how to recover an SD card on Mac or the dedicated guide to corrupted SD card recovery on Mac.
Recover Missing SD Card Files With Recoverit
Security Verified. Over 7,302,189 people have downloaded it.
Part 3. Check And Repair Logical SD Card Errors On Mac
Once important data is safely copied or recovered, start with Disk Utility for the simplest guided check. Use Terminal only when you want a verification-only command, need clearer text output, or Disk Utility's interface is not responding. Both routes examine logical storage structures; neither is a physical flash-health test.
Method 1. Run Disk Utility First Aid
According to Apple's current Disk Utility guide, First Aid checks and can fix errors related to a storage device's formatting and directory structure. Apple also states that it cannot detect or repair every disk problem.
- Open Disk Utility: go to Applications > Utilities > Disk Utility, or search for it with Spotlight.
- Show the full device tree: choose View > Show All Devices.
- Identify the SD card carefully: match its name and capacity. Do not select your Mac's internal startup disk.
- Start with the volume: select the indented volume below the physical card, click First Aid, and then click Run.
- Work upward: after checking each volume, run First Aid on any container shown and finally on the physical SD card. Most camera cards use FAT32 or exFAT and may not show an APFS container.
- Read the details: if Disk Utility says the card appears to be OK or was repaired, eject it, reconnect it, and verify your files. If the repair fails, do not keep writing to the card; follow Part 6.

Safety note: First Aid is not an undelete tool. Because a repair can update file-system metadata, recover missing files first. Never click Erase unless you have a verified backup or have already recovered everything important.
Method 2. Verify The SD Card In Terminal
Terminal exposes the same macOS disk-management framework with explicit commands. verifyVolume checks file-system data structures; repairVolume attempts to repair them. The example identifier below is only a placeholder because macOS can assign a different disk number whenever devices are reconnected.
- Open Terminal: go to Applications > Utilities > Terminal.
- List external physical devices: run the following command.
diskutil list external physical - Confirm the correct volume: identify the SD card by capacity and name. A volume identifier may look like
/dev/disk3s1. Recheck after every reconnect. - Run a verification-only check: replace the example identifier with the SD card volume's actual identifier.
diskutil verifyVolume /dev/disk3s1 - Repair only after the data is safe: if verification reports repairable file-system errors, use the actual volume identifier in the command below.
diskutil repairVolume /dev/disk3s1
The real Terminal capture above shows the diskutil verifyVolume output pattern on macOS. Your identifier, volume name, and file-system checker will differ. Screenshot source: Pandora Recovery.
Do not substitute the whole-disk identifier blindly. diskutil verifyVolume normally targets a mounted file-system volume such as disk3s1. By contrast, diskutil verifyDisk /dev/disk3 checks the partition-map layout; it does not scan for bad blocks.
Part 4. Test An SD Card's True Capacity And Write Reliability
First Aid can report a clean file system even when a counterfeit or failing card cannot reliably store its advertised capacity. After all valuable data is backed up or recovered, a full write-and-read test can answer that separate question. This test is intentionally placed after recovery because it writes a large amount of data.
Method 3. Run An F3XSwift Write-And-Read Test
F3XSwift is an open-source macOS interface for the F3 tools. The project's current documentation states that it supports macOS 13 or later, including macOS 26, on Apple silicon and Intel Macs. It uses f3write and f3read to test usable capacity and detect obvious read/write failures.
Use it only after backup or recovery. F3XSwift fills available space with test files and then reads them back. The safest setup is an empty card that you are prepared to erase or reformat. Do not run it on a card that still contains the only copy of important data.
- Download from the official project: open the GitHub releases page linked from the repository and download the current app build.
- Connect the backed-up card: confirm that macOS mounts it and that no needed files remain only on the card.
- Select the SD card: open F3XSwift, choose the correct removable volume, and click Test.
- Grant access: approve the macOS file-access prompt so the app can create test files on the selected card.
- Let both phases finish: the write stage fills available space; the read stage verifies the written patterns. Large or slow cards may take hours.

- Interpret the result: a successful test supports the tested capacity and current read/write reliability. A failure, data mismatch, or much smaller usable capacity is a reason to replace or return the card.

Both interface captures come from the official F3XSwift documentation.
A pass is not a lifetime guarantee. It does not reveal remaining NAND endurance or prove that the card will survive future heat, power loss, impact, or heavy recording.
Part 5. Fix SD Card Errors By Symptom
Use the symptom that matches what your Mac actually shows. This avoids destructive formatting when the real cause is a locked adapter, hidden Finder setting, unsupported encryption, or failing reader.
| Symptom | Likely Cause | What To Do |
| The card appears in Disk Utility but not Finder. | The volume is unmounted or external disks are hidden in Finder. | In Disk Utility, select the volume and click Mount. Then open Finder > Settings > General and Sidebar and enable External disks. |
| The card is missing from Disk Utility. | Reader, adapter, port, contact, accessory approval, or physical card failure. | Unlock the SD adapter, reinsert the card, try another known-good reader and port, and test another Mac or the original camera. On an Apple silicon Mac laptop with macOS 13.3 or later, approve the new accessory if prompted. |
| The card is read-only. | The full-size SD adapter's lock slider is engaged, or the card controller has forced a protective read-only state. | Move the lock slider to the unlocked position and reinsert it. If multiple readers still report read-only, copy or recover the files and replace the card. |
| macOS says the disk is unreadable or not initialized. | Unsupported or damaged file system, partition damage, encryption, or an unformatted card. | Click Ignore if files matter. Recover first, then use First Aid. Initialize or erase only after the data is safe. |
| The card is BitLocker-encrypted. | macOS does not natively unlock BitLocker volumes. | Use a compatible Windows PC and the password or recovery key to unlock and copy the files. Do not format merely because macOS cannot open it. |
| First Aid succeeds, but errors return. | Unstable flash memory, reader problems, unsafe ejection, power loss, or a recurring camera/device issue. | Replace the reader for comparison, back up immediately, run F3XSwift only after the data is safe, and retire the card if corruption recurs. |
| First Aid cannot repair the card. | Severe logical corruption or physical failure. | Recover or copy what you can. Then reformat the card in the device that will use it. If formatting fails or errors return, replace the card. |

For a device that is absent from Disk Utility, use the dedicated Mac not recognizing an SD card guide. If the card needs a fresh file system after recovery, follow the FAT32 SD card formatting guide for Mac or the broader microSD card formatting guide. Formatting erases the card and is a last resort, not a recovery step.
Part 6. Understand The Test Results
| Result | Meaning | Next Action |
| First Aid reports the card appears to be OK. | No repairable logical problem was found in the structures checked. | Verify files, eject safely, and monitor the card. This result does not prove physical health. |
| First Aid reports that the card was repaired. | Disk Utility changed one or more logical structures. | Copy the files again and compare them with your backup. If errors return, replace the card. |
verifyVolume reports the volume appears to be OK. |
The selected file-system structures passed the current check. | No repair command is needed unless another verified symptom remains. |
First Aid or repairVolume fails repeatedly. |
The corruption is too severe for an in-place repair, or the hardware is unstable. | Stop repeated repairs, recover data, reformat once, and replace the card if it still fails. |
| F3XSwift reports mismatches or less usable capacity than advertised. | The card may be counterfeit, defective, or failing. | Do not trust it with new data. Return or replace it. |
| No device detects the card. | There is no software-accessible storage device to scan. | For valuable files, stop testing and contact a recovery lab. Otherwise replace the card. |
Part 7. Prevent Repeat SD Card Errors
- Use the camera or device's Format function after the files are backed up, rather than repeatedly deleting individual files across several devices.
- Eject the card in Finder before removing it from a Mac, and wait until the camera finishes writing before opening the card door.
- Avoid removing the card during import, firmware updates, recording, or formatting.
- Use reputable cards from authorized sellers and choose the capacity and speed class recommended by the camera or device maker.
- Keep at least two verified copies of important photos or footage before reusing a card.
- Replace a card that becomes permanently read-only, repeatedly corrupts files, fails a full F3 test, overheats, or has physical damage.
- Do not rely on one high-capacity card as the only copy of an entire shoot.
FAQ
-
How do I check an SD card for errors on a Mac?
Copy or recover important files first. Then open Disk Utility, choose View > Show All Devices, select the SD card volume, and run First Aid. For a verification-only command, identify the volume withdiskutil list external physicaland rundiskutil verifyVolumewith its actual volume identifier. -
Can a Mac show the remaining life of an SD card?
Usually not. Most consumer SD and microSD cards do not expose useful S.M.A.R.T. endurance data through common Mac card readers. macOS can check detection, logical file-system consistency, capacity, and current read/write behavior, but it normally cannot report reliable remaining flash life. -
Does Disk Utility First Aid recover deleted files?
No. First Aid checks and repairs formatting and directory-structure errors. It is not an undelete tool. If files are missing, scan the card with recovery software before First Aid, repair commands, or formatting. -
Can First Aid make SD card data loss worse?
A repair changes file-system metadata, so there is risk when a card is severely corrupted. Copy readable files or recover missing files first. First Aid is appropriate after the data is safe, not as the first response to missing photos or videos. -
Is diskutil verifyVolume safe for an SD card?
diskutil verifyVolumeis the verification command and does not intentionally repair the file system. Still, confirm the device identifier carefully and avoid extra activity on an unstable card.diskutil repairVolumeis different because it writes repairs. -
Does diskutil verifyDisk check an SD card for bad blocks?
No.diskutil verifyDiskchecks the partition-map layout. It is not a surface scan or flash-wear test. Use a full F3 write-and-read test only after backup or recovery if you need to validate capacity and obvious read/write defects. -
Can I run F3XSwift without erasing my files?
F3XSwift writes test files into available space and then reads them back. Although it is designed to use free space, the safest practice is to use it only after all important data is backed up or recovered, preferably on an empty card. Do not stress an unstable card that still holds the only copy of valuable files. -
What if the SD card is not detected in Disk Utility?
Unlock the adapter, try another known-good reader and port, and test another Mac or the original camera. On an Apple silicon Mac laptop with macOS 13.3 or later, approve the accessory if prompted. If no device detects the card, software recovery cannot access it; consider a professional lab for valuable data. -
Should I replace an SD card after First Aid repairs it?
Not automatically, but back up the files and watch for repeat errors. Replace the card if corruption returns, it becomes read-only, F3XSwift reports mismatches, capacity is false, the card overheats, or more than one reader has trouble writing to it.