How to Test a USB Flash Drive for Fake Capacity and Counterfeit Storage

Overview

A fake USB flash drive is usually a real, low-capacity device whose firmware has been altered to report a much larger size. For example, a drive may appear to be 1 TB while physically containing only a fraction of that capacity. The operating system accepts the reported figure, but once the real storage area is filled, new data may overwrite earlier files or produce read and write errors.

Capacity testing is different from a quick copy test. Copying a few photos only confirms that a small amount of space works. A proper test writes data across the available space and then reads it back, which can take hours on a large or slow drive. Treat every newly purchased drive as untrusted until it passes a full test, especially before using it for photos, backups, recovery media, or important documents.

There are two useful approaches:

• Destructive testing: the test fills or reformats the drive. It is generally the clearest method, but all existing data must be backed up first.
• Non-destructive testing: the test works around existing files or uses only available space. It can reduce risk, but it may not examine every sector and is less conclusive on a partly full drive.

Capacity is also labeled in decimal units by manufacturers: 1 GB means 1,000,000,000 bytes. Operating systems may display a smaller number using binary-style units such as GiB, sometimes still labeled “GB.” A modest difference is normal; a drive that shows a tiny usable capacity after a full test is not.

Checklist by scenario

Before testing: inspect the listing and packaging

• Save the product page, order confirmation, seller name, photos, and promised capacity before the listing changes.
• Check whether the brand, model, serial number, connector type, and capacity agree across the packaging, device, and operating system.
• Be cautious of unusually large capacities at an implausibly low price, vague branding, misspelled labels, inconsistent logos, or packaging that looks reused.
• Look for reviews describing files disappearing, capacity changing, slow writes, or a drive becoming read-only. Treat review photographs as clues, not proof of authenticity.
• Do not assume USB-C proves high speed or high capacity. USB-C describes the connector; the underlying drive can still use slower USB technology.

For speed terminology and the difference between USB 2.0, USB 3.x, and newer standards, see our USB flash drive speed guide. A slow result alone does not prove counterfeit capacity, because performance varies by controller, file size, temperature, and the host port.

Windows: use a full write-and-read test

1. Copy off any files you need, then safely eject and reconnect the drive so you know which volume is being tested.
2. Confirm the drive letter and displayed capacity in File Explorer. Never rely on the drive letter alone when multiple removable disks are connected.
3. Use a recognized capacity-testing utility such as H2testw or another maintained tool obtained from a trustworthy source. Verify the download and scan it before running it.
4. Choose the correct removable drive and select the option to use all available space. Read the warning carefully: a complete test may overwrite existing files.
5. Allow the write phase to finish, then allow the read-and-verify phase to finish. Do not judge the drive from the first few gigabytes.

H2testw commonly reports how much data was written and verified, the usable capacity, and any corrupted or missing areas. A result showing that only part of the advertised capacity is reliable is strong evidence of a fake-capacity drive. If the full capacity is verified but errors occur, the device may be defective, disconnected, overheating, or affected by a problematic USB port.

macOS: test the volume without guessing the disk

1. Open Disk Utility and identify the drive by its manufacturer, size, and connection. Disconnect other external drives if there is any doubt.
2. Back up the contents. For a destructive test, erase and format the correct external volume in Disk Utility, then close applications that might access it.
3. Install a reputable capacity-testing tool such as F3 from a trusted package source. F3’s usual workflow writes test files to a mounted volume and then verifies them.
4. Run the write stage on the selected USB volume, followed by the read stage. Confirm the path before starting; a mistaken path can affect files on another disk.
5. Record the amount verified and every reported corruption, damaged area, or missing file.

On macOS, the command-line disk name shown by diskutil list is not the same as the mounted folder path used for file-based testing. If you use Terminal, inspect the output carefully and avoid destructive commands unless you have identified the external disk beyond doubt. When the drive is not mounting, first use our guide to troubleshoot a USB flash drive that is not showing up.

Linux: identify the device, then run F3

1. Run a device-listing tool such as lsblk and identify the USB drive by model, size, and mount point. Do not proceed based only on /dev/sdX, because device letters can change.
2. For a file-based test, install F3 through your distribution’s package manager or obtain it from a trusted project source.
3. Run f3write against the mounted USB volume, then run f3read after the write phase finishes.
4. Review the verified capacity and error summary. Keep the terminal output or redirect it to a text file for your records.

Some Linux tools can test a raw device directly, but raw-device commands are destructive and easy to misapply. If you use one, unmount the correct USB device first and double-check the identifier. If you are not completely certain, use the mounted-volume workflow instead.

When you need a non-destructive check

First make a backup, then use a test that creates files only in unused space. This is safer for a drive containing data, but it cannot validate occupied areas without reading them and may leave less room for a meaningful test. You can also copy a large set of checksummed files, eject the drive, reconnect it, and compare the checksums. That is useful as an initial screen, not a substitute for a full capacity test on an empty drive.

What to double-check

• Capacity versus usable capacity: normal formatting overhead and decimal-versus-binary display differences are expected. A dramatic shortfall is not.
• Read errors versus write errors: write failures can indicate bad flash memory, a failing controller, or counterfeit capacity. Read-back mismatches show that data could not be retrieved reliably.
• Connection stability: repeat a suspicious result on another known-good port, without a hub or questionable cable. For a USB-C drive, try a compatible data port rather than a charging-only connection.
• Filesystem limits: an individual file may fail because of the filesystem, not because the drive is fake. For example, some formats impose per-file limits. A capacity tool that creates many test files helps separate this issue from missing storage.
• Test scope: a short benchmark measures speed, not authenticity. A drive can post a plausible burst speed and still fail when its actual capacity is exceeded.
• Physical identity: save screenshots of the label, connector, serial information, reported capacity, and test result. Photograph the packaging beside the drive if you are preparing a dispute.

Do not reuse a drive that fails verification for important storage. If the data is valuable, stop writing to it and consult a recovery workflow; our guide to file recovery software for USB drives and other storage covers the next steps.

Common mistakes

• Testing the wrong disk: disconnect unrelated storage and confirm model, size, and mount point before every test.
• Skipping the backup: destructive tests do exactly what they say. Treat the drive as disposable during testing.
• Stopping after a quick copy: a few gigabytes can fit inside the real capacity of a counterfeit drive.
• Confusing speed with capacity: a slow drive is not automatically fake, and a fast-looking benchmark does not establish authenticity.
• Using an unknown utility: download testing software from a reputable project or package source, scan it, and avoid “driver” installers or browser extensions offered by random download pages.
• Formatting away evidence: save screenshots and logs before reformatting or returning the product.
• Trusting the marketplace badge: seller status and platform labels do not replace a capacity test. Keep the listing and seller details in your evidence folder.

For a refund or dispute, provide the order number, seller and listing URL, advertised capacity, device photographs, operating-system details, tool name and version, full test log, and a concise explanation of the failure. Follow the marketplace’s current return instructions, but do not claim a specific policy outcome unless you have confirmed it for your order.

When to revisit

Use this checklist whenever you buy a new flash drive, receive a heavily discounted storage device, or prepare a drive for an important backup. Recheck a drive after unexplained file corruption, repeated disconnects, a sudden change in reported capacity, or a failed write. A drive that passes once can still wear out later; capacity verification is not a substitute for maintaining multiple backups.

Before seasonal shopping periods, revisit the testing-tool instructions and download sources because interfaces and supported operating systems can change. Also check whether your computer has recognized the drive under a different name or mount point. Keep a short record of the tool used, test date, verified capacity, and any errors so the result remains useful months later.

Practical final checklist: save the listing, photograph the product, back up existing files, identify the correct disk, run a complete write-and-read test, save the log, and do not trust the drive with irreplaceable data until it passes. For ongoing protection, pair tested storage with a broader backup strategy for photos and documents.