Mac Disk Benchmark: How to Test Your SSD Speed

When a large file copy feels slow, a Mac disk benchmark can tell you whether storage throughput is part of the problem. The useful answer does not come from one dramatic speedometer reading, though. Close active transfers, test the correct drive, repeat the same workload, and compare the middle result—not the single highest number.

That method works for an internal Mac SSD, an external SSD, a hard drive, or a fast memory card. It also gives you something more valuable than a screenshot: a baseline you can reproduce later.

Quick Answer: How to Test SSD Speed on a Mac

For a reliable Mac SSD speed test:

1. Stop backups, cloud sync, downloads, exports, and large file copies.
2. Confirm that you are testing the intended internal or external drive.
3. Run one warm-up benchmark.
4. Run three more tests with the same tool and settings.
5. Record the median read and write speeds in MB/s.

Use the same Mac, port, cable, enclosure, free-space level, and benchmark tool when you compare results later. A different workload can produce a different number without anything being wrong.

What a Mac Disk Benchmark Actually Measures

A disk benchmark writes and reads test data, then reports throughput. The two headline numbers are:

• Read speed: How quickly the drive can deliver data to the Mac.
• Write speed: How quickly the drive can accept data from the Mac.

Most simple speed-test tools emphasize large, sequential transfers. That is useful for copying videos, opening large project files, or checking whether an external SSD and its connection are performing consistently. It does not fully describe small-file work, latency, app launch behavior, or random input/output.

Three measurements are easy to confuse:

Use a benchmark to measure speed. Use Activity Monitor to make the test quieter. Use drive-health information when you are investigating reliability.

Step 1: Prepare the Mac for a Repeatable Test

The preparation takes longer to explain than to do, but it is where most misleading results begin.

1. Connect power if you are testing a MacBook. Keep the same power state for later comparisons.
2. Stop storage-heavy work. Pause Time Machine, cloud synchronization, downloads, video exports, virtual machines, and large copies when practical.
3. Check current disk activity. Open Applications > Utilities > Activity Monitor, select Disk, and watch the bottom graph for a moment. Apple explains that this view tracks reads and writes; it is a noise check, not a speed test.
4. Identify the target drive. Write down whether it is internal or external, its capacity, and—for external storage—the port, enclosure, hub, and cable.
5. Note the test conditions. Record the benchmark app and version, available space, and anything still writing in the background.

The screenshot above shows why checking first matters. Even an otherwise quiet Mac can have background writes, and those transfers compete with the benchmark for storage bandwidth. You do not need a perfectly idle system. You need conditions you can describe and repeat.

Tip: Test an external SSD while it is connected directly to the same port you plan to use. A different hub, cable, or adapter changes the path you are measuring.

Step 2: Run Sensei Disk Benchmark

As of August 2026, Sensei 2.1.2 keeps Benchmark, drive information, Health, and Statistics in the same Storage area. The route is:

1. Open Sensei.
2. Select Storage in the sidebar.
3. Choose the drive you want to test.
4. Open Benchmark.
5. Click Run Benchmark.
6. Wait until the read and write tests finish, then record both results.

The selected drive matters. If you meant to test an external SSD but opened the internal drive, the result answers the wrong question.

The August 2026 capture returned 1,842 MB/s read and 1,025 MB/s write on the working Mac. It is not a model-specific baseline: Activity Monitor still showed background writes during the session, and the history in the same screen demonstrates how much results can move between runs. The screenshot documents the current workflow, not a claim about what every Mac should reach.

Step 3: Repeat the Benchmark and Record the Median

One result is a sample. A small set is a baseline.

Use this simple protocol:

1. Run one warm-up test and do not record it.
2. Wait until background disk activity settles.
3. Run three recorded tests under the same conditions.
4. Sort each set of numbers and keep the middle read result and the middle write result.

For example, if three write results are 980, 1,030, and 1,140 MB/s, record 1,030 MB/s. The median reduces the influence of one unusually fast or slow pass without pretending that the variation did not happen.

Keep a note like this:

Tip: Do not average results from different benchmark apps. Two tools can use different block sizes, test files, cache behavior, and run lengths.

Alternative: Blackmagic Disk Speed Test

Blackmagic Disk Speed Test is a focused alternative, especially when your question is whether a drive can sustain large video transfers. Blackmagic’s official Mac App Store listing says it writes large blocks of data and continues testing both writes and reads over time.

Before starting, verify the target drive in the app’s settings. Then let the test complete multiple read/write cycles and note a stable range rather than saving the first peak.

Choose the tool that matches the question:

• Sensei: A quick benchmark with previous results, drive information, live I/O statistics, and health tools in the same app.
• Blackmagic Disk Speed Test: Repeated large-block tests with video-format indicators.
• Activity Monitor: Live process activity only; useful before a test, not a replacement for one.

The important rule is consistency. Pick one benchmark for your baseline and use that same tool when you test again.

How to Read Mac SSD Benchmark Results

Read and write speeds serve different work

Read speed matters when opening or copying data from the drive. Write speed matters when saving, exporting, recording, or copying data to it. It is normal for the two numbers to differ.

MB/s and GB/s are throughput units

Benchmark apps may display MB/s or GB/s. A result of 1.84 GB/s is roughly 1,840 MB/s in the decimal notation these interfaces commonly use. Keep the displayed unit in your notes instead of adding unnecessary precision.

“Good” depends on the complete storage path

There is no honest universal “good SSD speed for Mac” number. Compare your result with:

1. Earlier results from the same drive and setup.
2. The drive maker’s specification for the same interface and workload.
3. A second run after you remove an obvious bottleneck.

Do not compare an external SATA SSD through a hub with a different-capacity internal Apple SSD and conclude that one is defective. You are measuring the drive, controller, enclosure, cable, port, file system, free space, temperature, and benchmark workload together.

Why Mac Disk Benchmark Results Change

A result can move between runs for ordinary reasons:

• Time Machine, cloud sync, Spotlight, downloads, or another app used the disk.
• The external drive used a different port, cable, adapter, or hub.
• The test reached a different cache state.
• The drive or enclosure became warmer during sustained work.
• Available space changed substantially.
• The benchmark tool or its settings changed.
• You tested a different volume or physical drive.

Small movement is expected. A large, repeatable drop under matched conditions deserves investigation.

What to Do When SSD Speed Looks Too Low

Work from the least disruptive check to the most consequential:

1. Rerun on a quiet system. Check Activity Monitor’s Disk tab and stop large transfers.
2. Confirm the target. Make sure the benchmark is running on the intended drive.
3. Remove connection variables. Attach an external drive directly, then try a known-good compatible cable and another suitable port.
4. Check available space. If the disk is nearly full, use How to Check Mac Storage before testing again.
5. Repeat the same three-run protocol. Compare medians, not peaks.
6. Cross-check with a second tool. Use this to confirm the direction of the problem, not to combine unlike scores.
7. Look at drive health and real symptoms. Unexpected disconnects, I/O errors, corrupted files, or a health warning matter more than one low benchmark.

If reliability symptoms appear, stop treating the situation as a speed contest. Make sure important data is backed up before you stress the drive again.

Tip: A benchmark result can help you locate a bottleneck, but it cannot repair one. Change one variable at a time so you know which change mattered.

Disk Speed Is Not the Same as Free Space

A fast SSD can still be nearly full, and a drive with plenty of space can still be connected through a slow link. If your actual problem is capacity, start with How to Free Up Disk Space on Mac. If the gray category is the mystery, use What Is System Data on Mac?.

Those jobs complement a benchmark, but they answer different questions.

Build a Baseline You Can Use Later

A useful Mac disk benchmark is a controlled comparison, not a race for the highest screenshot. Test the right drive, quiet the system, repeat the same workload, and keep enough context to reproduce it.

Sensei is a practical choice when you want that speed result alongside live I/O statistics and drive-health information. Just keep the categories straight: throughput tells you how fast this workload ran; health data and real symptoms tell you whether the drive needs attention.

Optimize Your Mac with Sensei

Monitor performance, clean storage, and manage Mac maintenance in one native app, with a full 7-day trial before you decide.

Download Free TrialView All Plans

Related guides:

• How to Check Mac Storage
• How to Free Up Disk Space on Mac
• What Is System Data on Mac?