Google Pixel SD card slow — what to do next (safe checks)

Hey! “SD card slow on a Google Pixel” is a common one — and the tricky part is that on Pixel phones the SD card is almost always external (through a USB-C OTG adapter or microSD card reader), so the slowdown can come from multiple places in the chain.

Before we touch anything risky (like formatting), I want to figure out where the bottleneck is: the card, the reader/adapter, the USB-C link, or the way files are being copied (lots of tiny files vs a few big ones).

Quick starting point — which situation matches you best?
• Slow when opening/browsing the SD card in Files by Google (folders take ages to load)
• Slow copy speed (photos/videos take forever to transfer to/from the card)
• Random stalls (starts fast, then drops to near-zero or freezes)
• Only some files are slow (e.g., many small files, or 4K videos)

Also: which Pixel model and Android version, and are you using a USB-C memory card reader or a USB-A reader with a USB-C adapter?

Perfect — “starts okay, then slows down hard” is a very specific pattern, and it usually points to one of these buckets:

1) Card performance limits (older card, low speed class, or lots of wear — sustained writes fall off).
2) Reader/adapter bottleneck (some readers are effectively USB 2.0 speed, or unstable under load).
3) File type pattern (thousands of small photos/thumbnails can be slower than one big video — random I/O vs sequential).
4) File system quirks (exFAT/FAT32 differences, or a card that’s starting to develop errors).
5) Phone state (thermal throttling, low battery mode, background photo backup, storage scanning).

Related phrases people search when this happens: “Pixel USB-C SD card reader slow”, “microSD transfer speed drops”, “Files by Google copy stuck”, “SD card takes forever to move photos”.

When it slows down, do you see an error (like “can’t copy” / “device disconnected”), or does it just crawl with no message?

That “unplug/replug temporarily helps” is a huge clue — it can mean the link is getting unstable under sustained writing, or the card is taking long internal pauses (which looks like a frozen progress bar).

Let’s keep this diagnostic and low-risk. I’m going to ask a few questions, and the order matters because I’m trying to separate card vs reader vs workflow:

• Card details: what brand/size is the microSD (e.g., 64/128/256GB), and do you see any marking like U1/U3, V30, A1/A2? (Even “Class 10” helps.)
• What are you copying: lots of small images, or fewer large videos? Roughly how many files at a time?
• Source app: are you copying from Google Photos, Files by Google, or another file manager?
• Phone condition: is the Pixel warm when this happens, and is battery saver on?

If you want, you can also compare behavior using an alternate route later (like copying a single big file) — but we’ll do it safely, and I’ll explain what each result means.

U1 + A1 is totally usable, but it also explains why “hundreds of photos” can feel slow: lots of small files means the card is doing many tiny writes (random I/O), not one smooth stream. That’s where slower cards and cheaper readers get exposed.

Two more “situational” questions (I’m not leading you to a reset — I’m checking risk points):

1) Free space: is the microSD almost full (like 85–95% used)? SD cards slow down a lot near full capacity because they have less room to shuffle blocks internally.
2) Where did the card come from: did it previously live in a camera, Switch, dashcam, or another phone? Mixing devices sometimes leaves a file system structure that’s “fine” but performs poorly for a phone workflow.

Also, just so you don’t waste time: Pixel phones don’t have a built-in SD slot, so when people say “Google Pixel SD card slow,” it’s usually actually “USB-C SD card reader slow” or “microSD write speed drops.” Your symptoms fit that exactly.

You’re thinking about it the right way — formatting is effective sometimes, but it’s also the highest-risk move if you don’t have a clean backup. So we don’t go there first.

Based on what you said, the most likely “why it feels slow” is a mix of:
• High fullness (90%) → less free space for the card to manage writes smoothly
• Camera history → file system layout optimized for big sequential video writes, not thousands of small photo writes
• Many small files → copy progress stalls because each file has overhead (and Android also scans/indexes)

Secondary/related keyword angle (naturally): this is the classic “microSD slow write speed”, “transfer speed drops over OTG”, “Files by Google stuck copying” situation — not necessarily “bad card,” but we should test for that too.

Here are safe checks that don’t change the card’s structure:
1) Small test transfer: try copying one larger file (like a single 500MB–2GB video) and see if it’s smoother than “hundreds of photos.” That separates “small-file overhead” vs “everything is slow.”
2) Reader sanity check: if you can, try the same card in a different USB-C reader (or even a computer) just to see if the slowdown follows the card or the reader.
3) Stability check: when it stalls, gently wiggle the reader/connector — if it disconnects easily, that points to a physical/adapter issue rather than the card itself.

When you copied hundreds of photos, were you doing Copy or Move? (Move can look “stuck” because it’s doing extra work and verifying.)

Good catch — “slow to appear after plugging in” can be normal if the phone is scanning a full card, but combined with stalls it can also hint the reader is struggling to maintain a clean connection.

Let’s stay in the safe zone and gather evidence, not guesses. Here’s what I want you to observe (no data loss, no formatting, no “wipe storage”):

• Mount time: about how long until the card shows up in Files by Google — ~5 seconds, ~20 seconds, ~60+ seconds?
• Copy behavior: does Copy behave differently from Move for the same batch size?
• Batch size effect: does 20 photos feel okay, but 400 photos crawls? (That’s a classic “small-file overhead + indexing” sign.)
• Free space effect: if you delete a few gigabytes (only if you’re already backed up), does it feel less stall-prone?

Also, because you mentioned Files: make sure you’re browsing the external drive section in a consistent way. If you want a reference, this page explains how Android’s Files app handles USB storage devices (it doesn’t “fix” speed, but it helps confirm expected behavior).
Files by Google Help: Use USB storage devices

If you’d like, we can also compare your symptoms with similar “storage slow” patterns in other guides (for example: Android storage full — what to do next, USB-C OTG not working on Android, or Google Photos backup stuck) — not because they’re the same problem, but because they share the same “background scanning slows transfers” behavior.

Next safe step is to classify the slowdown so you don’t accidentally choose a “big fix” for the wrong cause.

Here’s a simple, non-destructive decision path (no formatting, no resets, no data deletion required):

A) Confirm it’s a “small files” problem vs an “everything” problem
Try two tests on the same SD card, using Copy (not Move):
• Test 1: Copy 20 photos (small batch).
• Test 2: Copy one large file (a big video or a single ZIP if you have one).
If Test 2 is smooth but Test 1 crawls, that’s a strong sign of small-file overhead + indexing, not a “dead card.” If both crawl, we suspect card/reader limits or connection instability.

B) Reduce scanning pressure
While you copy, avoid multitasking that triggers media scans: keep Google Photos from aggressively syncing, don’t open the gallery repeatedly, and try to leave the phone screen on with Files in the foreground. (This doesn’t “fix” anything; it just makes the test results clearer.) If you want a related read later: Android phone running slow after update can overlap with background indexing behavior.

C) Check the “near full” effect without committing to formatting
A card at ~90% full often behaves worse. If you already have a backup elsewhere (computer/cloud), freeing up space can dramatically change consistency. If you don’t have a backup, don’t delete anything yet — we can still proceed with A/B tests first.

D) Validate the card type expectation
U1 cards can be legitimately slow for sustained write + lots of files. That’s not a defect; it’s a spec reality. If you’re curious what the symbols mean (U1/U3, etc.), this is a clean reference:
SD Association: Speed Class overview

If you reply with (1) approximate copy speed you see when it’s “fast” vs “slow,” (2) whether the big-file test behaves differently, and (3) how full the card is, I can tell you which branch you’re in — workflow overhead, card limits, or reader/connection — and what the safest next check is for that branch.