An external SSD often slows down during a large write because the first part of the transfer lands in a fast cache and the rest must be committed at the sustained speed of the NAND, controller and enclosure. Heat, a lower-speed USB path, a slow source drive, thousands of small files, low free space or operating-system behavior can create a similar graph. The useful question is therefore not “Why is my SSD slow?” but “When does the speed change, in which direction, and under what repeatable condition?”
A sudden step down after roughly the same amount of data usually points toward cache exhaustion. A later decline that becomes worse as the enclosure heats and improves after cooling is more consistent with thermal control. A hard ceiling from the first second suggests the port, cable, hub, enclosure bridge or source device. Speed that collapses only with folders of small files is normally a workload problem rather than a failed sequential-write path. Record the shape before buying a replacement.
Direct answer: For large-file work, compare the settled write rate after the cache is full, not only the opening peak. Test directly from a known-fast source, use a verified data cable and port, leave useful free space, log time and temperature, then change one variable per run. Replace hardware only after the repeated curve identifies the limiting layer.
The Transfer Graph Usually Has Three Different Speeds
The number in a copy window is not a direct window into NAND. At the beginning, the operating system may buffer data in memory, the SSD may accept writes into pseudo-SLC cache, and the source may still be reading from its own cache. The displayed speed can therefore exceed what the destination can maintain for the entire job. This is normal as long as buffered data is eventually committed correctly and the settled rate matches the product’s workload class.
After enough data arrives, the fast area fills. The controller must move data into denser TLC or QLC cells while accepting new writes. That work reduces the available write rate. If the job continues, enclosure temperature, controller power limits and reduced free blocks can push the curve lower again. Different capacities of the same family may behave differently because they can use different NAND layouts, parallelism and cache sizes. A 10GB review test cannot establish how a 500GB backup behaves.
The position and shape of each decline provide more diagnostic value than the opening peak.Alt text: Conceptual external SSD transfer curve showing host burst, cache exhaustion and later heat or fullness effects.
Use the Shape of the Slowdown to Find the Layer
Before changing settings, capture four facts: the direction of the copy, the amount already transferred when speed changes, whether the enclosure is hot, and whether the same pattern repeats after a cold start. Also note whether the source is an internal NVMe SSD, another external drive, a memory card, a phone or a network share. The destination cannot write faster than the source can supply clean data.
A hard ceiling, a repeatable step and a temperature-linked decline call for different tests.Alt text: Diagnostic tree mapping observed external SSD slowdown patterns to likely layers and next checks.
Treat the ranges in the diagram as clues, not guarantees. File Explorer and Finder averages can fluctuate; bridges report differently; encryption and security tools add work; some controllers recover cache during pauses. The goal is to isolate a layer. If moving the same drive and cable to a verified faster port raises the ceiling immediately, the original port was limiting. If every host shows a similar cliff after the same written amount, the SSD’s cache and native flash behavior deserve attention.
Cause One: The Fast Write Cache Is Full
Many consumer SSDs treat part of their NAND as if it were one-bit SLC because SLC-style programming is faster than writing the cell at its full TLC or QLC density. Some cache is fixed and some is dynamic, so the available amount can shrink as the drive fills. The controller later folds cached data into its final form. During a long uninterrupted write, incoming data can outrun that folding process and the drive falls to a post-cache rate.
Cache exhaustion has a recognizable signature: a strong opening plateau, a relatively sharp step down after a repeatable amount of data, and a lower but often stable second plateau. Letting the drive idle may restore the first plateau because the controller has time to fold data and recover cache. This is not the same as thermal throttling, although both can occur in one run. A drive can exhaust cache while cool, then throttle later as sustained work continues.
How to verify it: Start with the drive cool and at a known free-space level. Write one file larger than the suspected cache while logging speed every 30 seconds. Repeat after a long idle. If the cliff returns at a similar written amount and the surface temperature is not tracking the change, cache behavior is the stronger explanation.
Cause Two: Heat Forces the Controller to Protect the Drive
Portable SSDs place an NVMe or SATA controller, bridge electronics and NAND inside a small enclosure. Sustained writes generate heat in all three. A metal shell can feel warm because it is moving heat away from the components; warm to the touch is not itself evidence of a fault. Throttling becomes likely when performance declines as temperature rises, stabilizes at a lower rate and recovers after the enclosure cools under otherwise identical conditions.
Log speed and enclosure temperature together; either measurement alone can mislead.Alt text: Technician measuring the surface temperature of a Digiera LPS2000M during a controlled large-file transfer.
Do not put an SSD on ice, against condensation or directly in a strong freezer stream. Instead, repeat the test at normal room temperature with the drive uncovered on a hard surface and adequate airflow. Compare the first and second run. If a magnetic SSD is attached to a phone, include the phone’s heat and case in the test because recording, charging and data writing can warm the combined stack. For a hub-style device, test with and without power delivery and attached accessories; charging heat and shared controller load can change the result.
Cause Three: The USB-C Chain Negotiated a Slower Path
USB-C describes the connector, not the data rate. The USB-IF identifies USB 3.2 Gen 1 at 5Gbps, Gen 2 at 10Gbps and Gen 2x2 at 20Gbps. A 20Gbps SSD connected through a 10Gbps host, a 5Gbps hub or a USB 2.0-only charging cable operates at the lowest common capability. Protocol overhead means usable file speed is lower than the link’s headline bit rate, and the SSD’s own sustained rate may be lower again.
Connect the SSD directly to the computer for the baseline. Remove docks, monitor hubs and extension adapters. Confirm the computer’s specific port specification because adjacent USB-C ports can differ. Use the supplied cable or a cable explicitly rated for the required data mode; wattage printed on a charging cable does not establish high-speed data support. If performance caps immediately at the same level on every file size, investigate the chain before blaming cache or heat.
Cause Four: The Source Cannot Feed the Destination
A copy is a pipeline. An external SSD can only write as quickly as the source reads, the CPU handles encryption or decompression, and the bus carries data. Copying from an SD card, an older SATA SSD, a network share or another device on the same hub can make the destination appear slow. A nearly full or busy internal source can also dip during the test. Copying between two external drives on one controller may divide bandwidth rather than providing two independent full-speed links.
Use a known-fast internal NVMe source for the destination-write test and reverse the direction for a read test. Keep a large test file on the source so it is not being downloaded or generated during measurement. Watch source-disk utilization as well as destination activity. If the destination writes quickly from the internal drive but slowly from a camera card, the camera card reader and card are part of the result.
Cause Five: Small Files Turn a Sequential Test Into Metadata Work
One 100GB video file is mostly a sequential stream. A 100GB folder containing hundreds of thousands of thumbnails, source files and sidecars requires repeated file creation, directory updates, permission checks and security scans. The progress window may pause between bursts even when the SSD can sustain a high sequential rate. This is why creative project folders can take far longer than an equally large camera master.
Compare the original folder with an archive containing the same data. A large improvement for the archive indicates per-file overhead. Archiving can be useful for transport or cold backup, but it changes accessibility and recovery granularity, so do not make it the only copy. Antivirus or content-indexing tools may amplify the small-file difference. Test with normal protections first; if you temporarily change a security setting for diagnosis, restore it and do not make broad exclusions for untrusted media.
Cause Six: Low Free Space and Background Work Reduce Headroom
Dynamic cache often depends on unused NAND. As the drive fills, the controller has fewer free blocks to treat as fast cache and less workspace for garbage collection. Performance near full capacity can therefore differ from a fresh review sample. File-system maintenance, encryption, snapshots, search indexing and backup verification can add background I/O at the same time. Reformatting may appear to “fix” the drive because it removes data and restores free blocks, but it also destroys evidence and files.
Record the free-space percentage before every run. If possible, retest after moving data elsewhere and allowing the SSD to idle while powered. Do not erase a drive solely to chase a benchmark. Check health data with a tool supported by the enclosure and controller, verify backups, and investigate unexpected errors, disconnects or read failures separately from a predictable performance plateau.
Run a Controlled 20-Minute Test
A useful test does not require a laboratory, but it does require a fixed workload. Choose one file of 50GB to 100GB, or larger if the first run never reaches a settled rate. Ensure the source is faster than the expected destination. Use the same port and cable, stop unrelated transfers, note room conditions and keep the drive on a hard surface. The objective is a curve with context, not a single screenshot.
The repeat and control stages distinguish a drive characteristic from a cable or temperature accident.Alt text: Twenty-minute external SSD test protocol with baseline, large write, cool-down, repeat and one-variable control stages.
- Record the computer model, operating system, SSD capacity, firmware if visible, file system, port, cable, hub status, free space and starting surface temperature.
- Copy one large file from a known-fast internal drive to the external SSD. Log displayed speed and cumulative data every 30 seconds; also record total elapsed time.
- Mark the amount written when any step down occurs. Continue long enough to observe a stable post-cache rate rather than stopping at the first decline.
- Eject safely, reconnect if appropriate, let the drive idle and cool, then repeat the exact workload. A different second curve can reveal cache recovery or accumulated heat.
- Change one variable only: try another certified cable, another verified port or direct connection instead of a hub. Repeat the same file.
- Run a folder of many small files and compare it with one archive of the same content. This separates sequential media speed from per-file overhead.
- Reverse the transfer to evaluate reads. Preserve the files and verify checksums when data integrity matters; speed without correct data is not success.
Windows and macOS Can Make the Same Drive Look Different
Windows removal policy changes caching behavior
Microsoft documents Quick removal and Better performance policies for external storage. Quick removal limits write caching so the device is usually ready to disconnect, while Better performance can enable caching and requires Safe Removal so pending operations finish. This setting can affect benchmark and copy behavior. Do not change it merely to inflate a screenshot; choose based on workflow and data-safety discipline, then disclose the policy when reporting results.
macOS copy completion still needs an eject
Finder may show a transfer finishing before every lower-level task you care about has settled, and Spotlight, thumbnail generation or backup software may continue using the volume. Watch Activity Monitor or an appropriate disk tool when diagnosing. Eject the drive cleanly before disconnecting. For comparisons, keep the file system constant because APFS and exFAT serve different compatibility goals and can behave differently with metadata-heavy folders.
Choose an External SSD by the Longest Write You Actually Perform
|
Workload |
What to measure |
Useful buying evidence |
|
Phone ProRes recording |
Minimum continuous write, heat, power stability and disconnects |
A complete recording-duration test on the exact phone, cable or hub configuration |
|
Daily photo ingest |
Large reads plus thousands of small sidecars |
Mixed-file copy time, not only sequential benchmark peak |
|
100–500GB project backup |
Cache cliff, settled write rate and total completion time |
Full transfer graph at a stated free-space level |
|
Editing from the SSD |
Sustained reads, random access and cable stability |
Application timeline test plus safe-eject behavior |
|
Occasional document transfer |
Reliability, portability and compatibility |
Peak performance is less important than verified capacity and clean reconnects |
A buyer moving 20GB at a time may remain inside the cache and never experience the lower plateau. A videographer who offloads 500GB after every shoot lives almost entirely in the sustained region. A phone recorder needs a stable minimum rate and connection for the whole take, not an impressive desktop burst. “Fastest” is therefore incomplete until the test size, direction, capacity, host, cable, free space and thermal state are stated.
Where the Digiera Portable SSD Range Fits
The Digiera LPS2000M ultra-thin MagSafe portable SSD is positioned for phone-attached capture and portable USB-C storage. Its current product page lists 1TB and 2TB variants, TLC NAND, a USB 3.2 Gen 2x2 interface and maximum read/write figures up to 2,000/1,800MB/s. Those are product specifications, not a published guarantee that every phone or computer will negotiate 20Gbps or sustain the maximum through a full-drive write.
Use the official product image whenever the enclosure, connector or DIGIERA branding must be exact.Alt text: Official Digiera LPS2000M ultra-thin magnetic portable SSD shown attached to an iPhone and as front and rear product views.
The Digiera 2-in-1 USB-C portable SSD adds a foldable direct USB-C connector, hub functions and a published 35W Power Delivery feature. That integration reduces loose cabling but creates a more complex test: storage traffic, charging, attached accessories, phone heat and connector leverage should be validated together. For long transfers, test direct storage alone first, then repeat with the intended microphone, power input or other accessory attached.
The direct-attach 2-in-1 design should be tested both as storage and as a shared hub under the intended accessory load.Alt text: Official Digiera 2-in-1 portable SSD with foldable USB-C connector and hub ports.
Compare both models and other form factors in the Digiera portable SSD collection. Before publication, the product team should standardize interface terminology across feature bullets, specifications and imagery. A page that says Gen 2x2 in one place and USB 3.0 or Gen 2 elsewhere makes it difficult for customers and reviewers to know which host capability is required.
What Not to Do When the Speed Drops
Do not stop the test at 5GB: A short benchmark may measure only host and SLC caching. Increase the test size until the speed curve settles.
Do not swap cable, port and file system together: A faster second run proves only that the combination changed. Alter one factor per run.
Do not cool the drive with condensation risk: Use normal airflow and room-temperature repeat tests. Water damage is not a diagnostic method.
Do not disable security permanently: Scanning can affect small-file copies, but broad exclusions expose real data. Use a controlled trusted dataset and restore settings.
Do not equate warmth with failure: A metal enclosure is supposed to conduct heat. Correlate temperature with repeatable throttling, errors or disconnects.
Do not reformat before backing up: Formatting destroys data and removes the state you were trying to diagnose. Preserve files and health evidence first.
A Purchase Checklist for Sustained-Speed Buyers
- Ask for a transfer graph or total copy time using a dataset larger than the fast cache, not only a one-minute synthetic score.
- Require the exact tested capacity. Parallelism and cache behavior can differ between 1TB, 2TB and other variants.
- Confirm the host port and cable used, including whether USB 20Gbps, USB4 or Thunderbolt was actually negotiated.
- Check settled write speed at a realistic free-space level and after a second warm run.
- For phone recording, validate the exact phone model, codec, frame rate, power state, mounting method and cable or direct connector.
- For a hub SSD, test charging and accessories simultaneously and record whether bandwidth, heat or power behavior changes.
- Prioritize data correctness, safe eject, warranty and repeatability over the single highest number on the package.
The Decision: Normal Behavior, Configuration Problem or Fault?
Probably normal cache behavior: The drive is fast for a repeatable amount of data, then settles at a stable lower rate without errors, disconnects or progressive deterioration. Compare that settled rate with independent capacity-specific testing before judging value.
Probably a configuration bottleneck: The speed is capped from the beginning, improves immediately on another port or cable, or changes when a hub is removed. Verify the negotiated link and source path.
Probably thermal control: The drop occurs later as the enclosure heats, becomes worse on a second warm run and improves after a normal cool-down. Improve airflow and assess whether the product suits the sustained workload.
Escalate as a possible fault: The SSD disconnects, reports I/O or file-system errors, corrupts verified data, becomes unreadable, shows abnormal health warnings or performs unpredictably across known-good hosts and cables. Back up immediately and use the manufacturer’s support process.
Decision Tables
Speed-Curve Interpretation
|
Observed pattern |
Most likely cause |
What to verify |
|
Fast start followed by one stable lower plateau |
SLC cache exhaustion or native NAND limit |
Transfer a file larger than the cache and monitor the full curve |
|
Repeated sharp drops and recoveries |
Thermal throttling, background work or power instability |
Log temperature, link state and system activity |
|
Hard ceiling near 450-550 MB/s |
5Gbps USB path or SATA-based enclosure |
Check negotiated USB speed and bridge specification |
|
Good large-file speed but poor folder copies |
File-count and metadata overhead |
Retest with one large file and an archived copy of the folder |
Controlled Retest Matrix
|
Variable |
Controlled test |
Interpretation |
|
Cable/port |
Direct connection with a known-rated short cable |
Improvement identifies the original path as the bottleneck |
|
Source drive |
Copy from a verified faster internal SSD |
Rules out a slow source or read contention |
|
Free space |
Retest below roughly 80% used capacity |
Large recovery suggests garbage-collection pressure |
|
Thermals |
Repeat from a cool start and log enclosure temperature |
Time-linked decline supports a thermal cause |
Frequently Asked Questions
Why does my external SSD start at 1,000MB/s and then drop?
The opening rate may use operating-system memory and the SSD’s fast pseudo-SLC cache. Once that cache fills, writes settle toward the native NAND and controller rate. If the drop happens after a similar amount of data in repeated cool tests, cache exhaustion is more likely than a random fault.
Is an external SSD slowing down because it is overheating?
Possibly, but temperature must correlate with the decline. If performance falls later in the run, worsens when the enclosure is already warm and recovers after cooling, thermal control is plausible. A warm metal case alone does not prove throttling because the case also acts as a heat spreader.
Does a USB-C cable support the full speed of every portable SSD?
No. USB-C is the connector shape. Cables and hosts can support USB 2.0, 5Gbps, 10Gbps, 20Gbps, USB4 or other modes. The complete path runs at the lowest supported data capability, so use a cable and port explicitly rated for the SSD’s required mode.
Why are thousands of photos slower to copy than one large video?
Each file requires creation, directory and metadata updates, permission work and often antivirus or indexing checks. One large video is mostly sequential. Compare the folder with a single archive of the same content to see how much per-file overhead contributes.
Does an SSD become slower when it is almost full?
It can. A fuller SSD may have less unused NAND for dynamic cache and less workspace for garbage collection. The effect depends on controller, firmware, NAND and workload. Record free space and retest after safely moving data elsewhere rather than reformatting first.
Can I trust the speed shown by Finder or File Explorer?
Use it as a trend, not the only measurement. The display can average bursts and pauses, and cached writes may continue below the visible copy layer. Record total elapsed time, cumulative data, repeated interval speeds and safe-eject behavior. Application tests matter when the workflow is editing or recording rather than copying.
What sustained-speed information should Digiera publish?
For each capacity, publish the test host, negotiated interface, cable, file system, free-space level, dataset size, ambient condition, first-cache region, settled write rate and total completion time. Phone products should add the exact model, codec, frame rate, power and accessory configuration. These details make peak specifications useful instead of ambiguous.
How large should a test file be to reveal sustained SSD speed?
It must be larger than the drive's dynamic or fixed write cache, which can vary with capacity and free space. For many consumer drives, use tens or hundreds of gigabytes and record the entire transfer. Stop treating the opening burst as sustained performance once the curve reaches a lower plateau.
Can exFAT cause an external SSD to slow during a long transfer?
The file system can affect metadata-heavy workloads, allocation and repair behavior, but a clean, large sequential transfer usually exposes the hardware path more clearly. Compare the same drive and file on a native file system only after backing up, and do not reformat merely to chase a brief benchmark difference.
Can antivirus or indexing create a saw-tooth transfer graph?
Yes. Real-time scanning, thumbnail generation, cloud synchronization and search indexing can periodically consume CPU or read the files being written. Retest after allowing background work to settle, then inspect system activity. If the pattern disappears, the SSD may be healthy even though the first user experience was inconsistent.
Why does SSD speed recover after I pause the copy?
A pause can let the controller fold cached data into NAND, reclaim blocks and cool down. Recovery therefore points toward cache pressure, garbage collection or thermals, but it does not identify which one alone. Compare temperature and free-space conditions, then repeat the same workload from a cool start.
Does TRIM help an external SSD maintain speed?
It can, when the operating system, USB bridge, enclosure firmware and drive all pass the command correctly. TRIM helps the controller prepare unused blocks; it cannot overcome a small cache, slow NAND or an overheated enclosure. Verify support rather than assuming every USB adapter exposes it.
When does sustained slowdown justify an RMA?
Escalate when a known-good host, cable and port reproduce performance far below the product's documented sustained behavior, especially with disconnects, errors or SMART warnings. Preserve the workload size, temperature, firmware, free space and speed graph. A normal post-cache plateau by itself is not proof of a defect.
Sources
- USB-IF USB 3.2 naming and 5Gbps, 10Gbps and 20Gbps guidance
- Microsoft Windows external storage removal and write-caching policy
- Tom's Hardware external SSD test methodology and sustained-write emphasis
- Tom's Hardware Crucial X6 cache saturation methodology
- Reddit r/ssd discussion of a repeatable speed drop after a fixed written amount
- Digiera LPS2000M ultra-thin MagSafe portable SSD
- Digiera 2-in-1 USB-C portable SSD