Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


When you get an “SD card not recognized” error, protect the data before trying to repair it. Power down when the device manual requires it, reseat the card without force, inspect the full-size adapter's lock tab, and test a known-good reader or compatible host. Do not initialize, format, erase, or accept a “fix” prompt until you know whether the card contains the only copy of important files.
“Not recognized” can mean the slot detects no hardware, the operating system sees a disk but no mountable volume, the device rejects the card standard or capacity, or the file system is damaged or unsupported. Those layers require different responses.
Key Takeaways
- Stop writes and preserve the card when important files have no verified backup.
- Check card orientation, adapter lock, reader, port, and supported SD standard before software changes.
- Use Disk Management or Disk Utility only to observe the current state at first.
- Android portable and adopted storage have different ownership and recovery limits.
- Format only a confirmed blank or safely backed-up card in the device that will use it.
For a general evidence-first process, begin with the device and app troubleshooting guide.
Stop repeated insertion and writing if the card is cracked, bent, delaminating, corroded, unusually hot, wet, or missing contact material. Also stop if the device freezes whenever the card is inserted, repeatedly asks to format it, reports the wrong capacity, or the card contains the only copy of valuable photos, recordings, or work.
Record the card brand, stated capacity, SD/SDHC/SDXC or microSD marking, last device that read it, last successful use, adapter and reader, and exact error. Photograph the card only if you can avoid exposing identifying labels. Do not share private file names, recovery keys, or screenshots of personal media.
Use this state table before acting:
| State | Meaning to investigate |
|---|---|
| No device appears anywhere | Card, adapter, reader, slot, port, or host enumeration |
| Disk appears, but no volume mounts | File system, partition, encryption, or corruption |
| Card works in camera but not computer | Reader, adapter, driver, or file-system support |
| Card works in computer but not camera/phone | Device capacity, standard, format, or slot compatibility |
| Card is readable but cannot save | Lock tab, permissions, full storage, wear, or read-only failure mode |
If files matter, make a read-only recovery decision before using repair tools. Repeated writes, formatting, or aggressive scans can overwrite structures needed for recovery.
Turn off the phone, camera, recorder, drone, console, or other appliance if its manual requires power-off insertion. Remove the card by its edges, check orientation, and reinsert it without force. Never trim a card, stack adapters, or use tape to make a loose card fit.
For a microSD card in a full-size SD adapter, inspect the adapter's side lock tab. The tab normally controls write-protect sensing in the reader; it does not encrypt the card. A loose or damaged tab can make the card appear read-only, but it usually does not explain complete hardware absence.
Cross-test one component at a time:
If the reader itself is missing, use the USB device recognition guide. If other cards work in the same slot but this one does not, the card or its format becomes more likely. If no card works, the slot, reader, driver, or host deserves attention.
Apple notes that SDXC-capable Mac slots support SD, SDHC, and SDXC media, while card insertion, mounting, and the lock slider can affect use.[2] Exact capacity and speed-class support still depend on the device, so check the manual rather than assuming every card bearing the same physical shape is compatible.
On Windows, open Disk Management and identify the removable disk by capacity. On macOS, open Disk Utility and choose Show All Devices. At first, observe only: does a physical disk appear, is there a partition or volume, is it mounted, and does the capacity look correct?
Do not initialize a previously used card because Windows labels it Unknown or Not Initialized. Do not erase a card because Disk Utility cannot mount it. These actions create new disk structures and may reduce recovery options. Microsoft describes Disk Management as the place to view disks and volumes, but its create, format, initialize, and delete operations are changes, not harmless visibility checks.[4]
If the physical disk appears with a healthy recognized volume but no drive letter, a careful letter assignment may restore Windows visibility without formatting. If the disk reports RAW, Unallocated, an unexpected capacity, or repeated disconnects, stop and decide whether recovery or replacement is safer.
Compare the external drive visibility guide for the distinction between physical disk, partition, volume, mount, and file-system state. An SD card adds adapter and device-compatibility questions, but the data-preservation rule is the same.
Check the card and device specifications together. Older devices may support SD or SDHC but not SDXC, may impose a capacity limit, or may require a specific file system. Cameras, recorders, consoles, and embedded devices can also create proprietary folders or databases even when the underlying file system is common.
Do not solve compatibility by downloading a random formatter or driver. The SD Association provides an official SD Memory Card Formatter and recommends it over generic operating-system tools for SD media.[3] Formatting still erases logical access to existing data, so use it only after backup or when the card is confirmed expendable.
For a new blank card:
For a previously used card, copy readable files first. A card that suddenly becomes read-only may be protecting failing flash memory; do not rely on it after merely copying files off. Replace it and verify backups.
Android can use an SD card as portable storage or, on devices that support it, format it as internal or adopted storage. Portable storage is intended for movable files. Adopted storage is tied to the phone and may contain apps or data that another device cannot interpret normally.
Google warns that formatting an SD card erases its data and explains that moving between portable and internal storage requires formatting.[1] Therefore, do not put an adopted card in a computer and format it because it looks unreadable. Return it to the original phone first and check whether the phone can mount or migrate the data.
If Android offers a “Set up” or format prompt for a card that previously worked, cancel until you confirm backups. Check Storage settings for the card, restart the phone, and test the card and slot separately. Do not clear device storage, factory-reset the phone, or delete app data to fix card detection.
When the phone's internal storage is the actual problem, use the Android storage guide. Moving data to an unreliable card is not a safe substitute for freeing and backing up internal storage.
Choose recovery before repair when files are important and not backed up. A qualified recovery provider is appropriate when the card is physically damaged, repeatedly disappears, reports the wrong capacity, causes readers to hang, or cannot be imaged reliably. Keep the card out of further use and store it in a protective case.
Format only when the data is safely copied or expendable, compatibility has been checked, and the target device's documented process is available. After formatting, write and read back several test files. A card that produces errors, becomes read-only again, changes capacity, or corrupts new files should be replaced rather than trusted.
Seek device service when several known-good supported cards fail in the same slot, contacts are bent, the card will not latch or eject normally, or the failure follows impact, liquid, or repair. Do not probe the slot with metal or compressed air. A removable reader is safer to replace than a damaged built-in slot, but only after the cross-test identifies it.
The microSD card, adapter contacts, reader, slot, or host may be at fault. Test another adapter and reader one at a time without accepting a format prompt.
The switch normally signals write protection through the reader. A damaged adapter can behave unpredictably, but the switch more often explains read-only access than total absence.
Not before confirming whether the card contains needed data. Formatting erases the existing logical structure and may reduce recovery options.
The computer's reader, adapter, driver, or file-system support may differ. Copy files through the camera if that is the only stable, supported path.
The phone may no longer recognize the file system or adopted-storage relationship. Cancel the prompt, check backups, and return the card to the original device before formatting.
Only if the device explicitly supports SDXC and that capacity. Physical fit alone does not prove electrical, standard, or file-system compatibility.
Check the adapter lock tab, but also treat unexpected read-only behavior as a possible flash failure. Copy readable data and replace a card that repeats the condition.
Use it when valuable files lack a backup and the card is physically damaged, unstable, wrong-capacity, repeatedly disappearing, or unreadable in known-good compatible readers.
Preserve the only copy of your files before considering formatting, and check whether the card and reader are compatible. Network changes do not resolve a damaged SD card or an incompatible reader; a VPN cannot recover the card or change that hardware compatibility.
Sources checked 4 September 2026.
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.