microSD A1 vs A2 vs V30: Match the Card to Your Device

Technology / Removable storage / Buying guide

A1 and A2 are application-performance classes; V30 is a video-speed class. They answer different questions, and a microSD card can carry both labels. Choose a card by matching the exact device’s supported card family, capacity, and required performance symbols before comparing advertised transfer speeds.

A card that is attractive for storing applications is not automatically the right choice for a camera’s recording mode. Likewise, a high video rating does not establish that a phone, handheld device, or small computer can use the card’s application features. The useful starting point is the manual for the device you own.

01 / Check the supported card family and capacity first

The SD Association’s compatibility guidance explains that card-family support matters. An SDHC host is not automatically compatible with an SDXC card. A speed label does not override that boundary.

Its capacity overview distinguishes SDHC, above 2GB through 32GB, from SDXC, above 32GB through 2TB. These are standard families, not a promise that an individual device accepts every capacity in the family.

For example, DJI’s handheld-device card list, checked on 28 October 2026, specifies up to 512GB for Osmo Action 4 and up to 256GB for Osmo Action 3. Similar-looking camera names do not justify carrying one limit across models.

Keep the source link with your purchasing notes. If you change the device or recording mode later, revisit that note instead of treating the card as universally compatible.

02 / Read A1, A2, and V30 as different capabilities

The SD Association’s application-class explanation covers minimum random and sequential performance under defined conditions. Random access matters when a workload touches many separate pieces of data rather than writing one continuous stream.

Video Speed Class addresses sustained recording performance. The Association’s explanation of card markings identifies V30 with a 30MB/s minimum continuous-write level under the class requirements. It is not a claim that every operation runs at exactly that speed.

Do not interpret A2 as a higher step on the same ladder as V30. A card labelled A2 and V30 is describing two aspects of its behaviour. Compare each with the requirement it is meant to satisfy.

Also distinguish a classification from a result you have measured. This guide explains documented labels; it does not claim a benchmark for any card, phone, or camera.

03 / For recording, follow the required symbols and card list

Find the specification for the exact recording mode you intend to use. Resolution alone is an incomplete shopping rule: the device manufacturer may distinguish modes, settings, or approved cards. Do not replace that information with a generic “good for 4K” label.

The SD Association’s speed-class guidance recommends matching the host’s class symbol with the same or a higher class in that family. It cautions against treating different class symbols as interchangeable merely because they refer to the same numerical rate.

For a hypothetical camera requiring V30, compare cards carrying the required video designation and meeting the other device conditions. An A2 badge alone does not answer that requirement. If the manual specifies several conditions, satisfy them together.

Use recommended lists precisely. A listing for one capacity or product identifier is stronger evidence for that item than for every similarly named card on a marketplace. When the list and a retailer’s description disagree, resolve the discrepancy before buying.

For unattended or long recording, also look for the manufacturer’s stated suitability for that duty. Do not treat a speed rating as an endurance, lifespan, or recovery guarantee. If endurance is important, make it a separate documented requirement.

04 / Check host support before expecting A2 benefits

The Association’s A2 documentation describes command queuing and cache features and explicitly states that A2 performance requires an A2-supported host together with an A2-supported card.

That is a reason to check the device documentation, operating environment, and manufacturer guidance. It is not evidence that every A2 card will make every application faster. Compatibility with removable storage and support for a performance feature are different claims.

For a hypothetical small computer running software from microSD, ask which card classes its current documentation recommends. Then consider what the task actually does: frequently opening many small files is different from copying a few large videos.

For a phone, first confirm what the device allows on removable storage. Buying an application-rated card does not itself enable application installation or change the phone’s storage policy. Avoid promising a capability from the card label that belongs to the host.

If the manual offers no clear A2 statement, do not invent one from the card slot’s appearance. Choose among documented compatible options, or ask the manufacturer a specific question about the model and intended workload.

05 / Consider the reader and computer connection separately

A card’s recording use and its computer offload workflow can have different bottlenecks. The SD Association’s bus-interface overview distinguishes interface capability from actual card speed and notes that observed performance depends on the device and operation.

Before paying extra for a headline transfer figure, read the product’s conditions. Check the supported reader, interface, capacity-specific specifications, and whether the quoted figure is for reading or writing. Keep those claims separate from the minimum recording class.

Trace the whole path: card, reader, computer port, and destination storage. If one part is unsuitable, buying a higher-labelled card may leave the actual transfer problem unchanged. Compare components around the task rather than ranking them by one printed number.

If the job is primarily transporting large files between computers, consider whether a memory card is the right form factor at all. Our USB flash drive vs portable SSD guide covers that separate purchase decision.

When checking an existing setup, record the exact reader and port used. A test through an unrelated adapter does not establish how the card will behave in the intended camera or application host.

06 / Compare only candidates that satisfy the device

Create a short comparison record with these fields: exact product identifier, capacity, required performance marks, host compatibility evidence, seller, warranty terms, and price. Use current local offers when you buy; this guide does not assume one price across the US, UK, Canada, or Australia.

Separate mandatory requirements from optional conveniences. If a candidate fails a required capacity or class condition, a discount does not repair the mismatch. Once the suitable set is established, compare price, availability, support, and any verified transfer advantage relevant to your equipment.

For a hypothetical buyer with two suitable cards, one may be cheaper while another has a transfer claim tied to a reader the buyer does not own. Include the reader’s cost only if the faster offload workflow is actually useful and documented.

Buy through a seller whose identity and return process you can verify. Retain the receipt and packaging information so a questionable or faulty item can be traced. Avoid making a card your only copy of important work simply because its label meets the required classes.

Capacity is a workflow decision too. Plan how often you can copy and verify recordings, how cards will be labelled, and where the separate copy will live. More storage does not remove the need for that process.

07 / Prepare the card and check the intended workload

Back up existing contents before formatting. Follow the host manufacturer’s preparation instructions. For computer formatting, the SD Association provides its SD Memory Card Formatter and explains the compatibility requirements. Formatting is preparation, not a way to turn an unsupported card into a supported one.

Do not apply a generic external-drive format choice to a camera without checking its instructions. The host’s card-family and file-system expectations remain relevant. If a device requests a format unexpectedly, preserve needed data before agreeing.

• Confirm the exact card and capacity against the device documentation.
• Prepare it using the prescribed workflow after preserving existing data.
• Use non-critical material to check the intended recording or application task.
• Reopen the resulting files and inspect them on the receiving system.
• Check the normal offload path with the reader and port you will use.
• Keep a separate verified copy before deleting original material.

This is a suggested verification plan, not a hands-on test result. One successful sample does not guarantee every future recording. If errors occur, preserve the files you can recover and investigate the card, preparation, host requirements, and transfer path before repeating important work.

Frequently asked questions