FIELD GUIDESource-led reference

P075 / Storage / Guide

SD versus microSD: start with the form factor

Compare physical form first; keep the remaining requirements separate.

The useful distinction

Use the side-by-side form records for recognition, then write a complete card requirement from the host manual.

Claim inspection dates: 2026-10-01 · Independent review pending

Guide note · not an individual product specification

The useful distinction

Understand the requirement.

SD and microSD identify different physical forms in the SD Association overview. The rest of the card requirement still includes capacity family, bus mode and performance class. [C075A]

Bounded facts, visible unknowns

Specifications and limits

SD versus microSD: start with the form factor facts and limitations
Comparison layerPhysical card form [C075A]
Not impliedSame host compatibility or same transfer speed [C075A]
Verified device listNot included. Check exact device and accessory documentation.
A boundary, not an omission to guess around.

This guide does not claim a generic adapter preserves every advanced SD mode or that a card works in a named device.

Before you connect

What to check

  1. Identify the card slot exactly.
  2. Record the accepted capacity family and maximum.
  3. Record the bus and recording-class requirement.
  4. Verify any chosen adapter with the relevant manufacturer documentation.
Trace a supported connection class →

Finish with the documentation

Build a short list of exact card, adapter and host references. Remaining unknowns are a reason to seek the specification, not a reason to guess.

Your next step

Move from the form to the requirement.

The source trail

Evidence for this page

AI-assisted inspection is not independent engineering review. Source scope and access limitations are disclosed below. Procedural checklists are editorial requirements, not hardware measurements.

C075ASource checked · pending review

SD and microSD identify different physical forms in the SD Association overview. The rest of the card requirement still includes capacity family, bus mode and performance class.

SD Association · SD Standard Overview ↗

Locator: Conventional-card paragraph and form-factor table: first-row counts and UHS-II / SD Express count ranges
Access: public page. Counts are scoped to named modes. The overview does not identify an exact card or host, and extra-row count does not establish implemented protocol.

S041: full source recordSD Association · Capacity: SD, SDHC, SDXC and SDUC ↗

Locator: Capacity ranges, file-system table and Form Factor Size rows
Access: public page. Nominal card envelopes are identification aids, not mechanical tolerances, socket footprints, pad positions or formatting instructions.

S042: full source recordSD Association · SD Speed Class ↗

Locator: Speed-class families and Best Combination between Speed Class Host and Card
Access: public page. Bus modes and performance classes are distinct. Shared numeric minima across different class symbols do not guarantee the requested host class; no particular video mode is approved.

S044: full source recordInspect review dependencies → (private workspace)

Claim scope: Named standard or manufacturer description only; procedural checks are editorial recommendations, not hardware tests.. Next review due 2026-12-30.

Suggest a correction to this field note →

Common questions

Questions this record can help resolve

Evidence behind this page

Scope first. Source second. Approval separate.

3 linked sources · 1 scoped claims · 0 sources with inspection/access flags.

Page scope: consumer_pilot

Assessment 2026-10-22 · earliest scheduled source review 2027-01-05. This is a recorded-date assessment, not a live source check. Page-level independent review is not established by this panel.

Inspect 3 source scopes, access limits and dates

S041 · SD Standard Overview

SD Association · Standards-organization domain · inspected 2026-10-07 · due 2027-01-05

Within inspection window

Scoped support: SD/microSD physical-form and generation-specific contact-count distinctions; no numbered assignments or fabrication drawing.

Not established / limitations: Counts are scoped to named modes. The overview does not identify an exact card or host, and extra-row count does not establish implemented protocol.

Locator: Conventional-card paragraph and form-factor table: first-row counts and UHS-II / SD Express count ranges

S042 · Capacity: SD, SDHC, SDXC and SDUC

SD Association · Standards-organization domain · inspected 2026-10-07 · due 2027-01-05

Within inspection window

Scoped support: SD capacity/file-system classes and nominal full-size SD and microSD envelopes; not host capacity approval.

Not established / limitations: Nominal card envelopes are identification aids, not mechanical tolerances, socket footprints, pad positions or formatting instructions.

Locator: Capacity ranges, file-system table and Form Factor Size rows

S044 · SD Speed Class

SD Association · Standards-organization domain · inspected 2026-10-07 · due 2027-01-05

Within inspection window

Scoped support: Minimum sequential-performance class symbols and same-family host/card matching under defined conditions.

Not established / limitations: Bus modes and performance classes are distinct. Shared numeric minima across different class symbols do not guarantee the requested host class; no particular video mode is approved.

Locator: Speed-class families and Best Combination between Speed Class Host and Card

Trace 1 claims to their source records

C075A · P075

SD and microSD identify different physical forms in the SD Association overview. The rest of the card requirement still includes capacity family, bus mode and performance class.

Claim scope: Named standard or manufacturer description only; procedural checks are editorial recommendations, not hardware tests.

Source links: S041 · S042 · S044 · Evidence trail → (private workspace)

Prepare this page for review → (private workspace)Read the evidence method →

Recorded evidence only. An inspection date, publisher label, source link or generated packet is not independent technical review, hardware testing, fabrication approval or a compatibility verdict.