Best USB Flash Drives for Ventoy, Kali Persistence and Linux Installers

A cheap USB stick and a fast one boot a Ventoy menu in about the same time. The gap opens once you run Kali Linux with persistence, because every package install, log line and settings change is written back to the stick. Measured 4K random write runs from 2.23 MB/s on a budget Kingston to 80.92 MB/s on the PNY PRO Elite V3, a factor of 36. That number, not the read speed on the box, is what decides the best USB flash drive for Ventoy and for a Kali live USB you plan to keep.

Original content from computingforgeeks.com - post 177439

We ranked five drives on independent CrystalDiskMark runs and maker datasheets. Then we built the boot chain in a lab, from the Ventoy install to Kali persistence and Secure Boot. One apt-get update plus one small package grew the Kali persistence image by 334 MB (Ventoy 1.1.18, tested October 2026 on Ubuntu 26.04). That growth, plus the small synced writes of a live session, puts random write at the head of the table.

Best USB flash drive for Ventoy, ranked by random write

The three USB-A sticks are ordered by measured 4K random write at queue depth 1. By our reading, that is the access pattern of a live system syncing logs, package state and settings. The SanDisk and the IODD are placed by use case, because neither has a published random-write run. Sequential read only matters while the ISO loads, and every stick here reads a 5 GB ISO end to end in under a minute on a USB 3 port.

Award	Drive	4K random write (Q1T1)	Seq. write	Price (check live)
Best for Kali persistence	PNY PRO Elite V3 256GB (USB-A)	80.92 MB/s	863 MB/s measured	about $80
Best value Ventoy stick	Samsung BAR Plus 128GB	26.92 MB/s	66 MB/s measured	about $40
Best for USB-C laptops	SanDisk Extreme PRO USB-C 256GB	not measured independently	900 MB/s rated	about $76
Budget installer stick	Kingston DataTraveler Exodia 256GB	2.23 MB/s	21 MB/s measured	about $26
ISO as an optical drive	IODD ST400 enclosure	depends on the SSD inside	about 250 MB/s cap (review)	about $114, no SSD

Prices are bands from the Amazon catalog on 25 October 2026 and move weekly, so check the listing and the seller before you buy. If you arrived from our Windows 11 bootable USB guide, any pick here holds that installer as well. The measured columns come from ssd-tester.com CrystalDiskMark runs on the exact capacities listed. We found no independent run of the SanDisk USB-C drive, so its row carries the maker rating and nothing else.

How the sticks and the boot chain were tested

Nothing in this guide was benchmarked on a physical stick in our lab, and the method below says exactly where each number comes from. Splitting it this way keeps lab facts and drive facts separate, which matters because a virtual disk tells you nothing about a flash controller.

• Drive speeds: CrystalDiskMark results from ssd-tester.com for the exact model and capacity: SEQ1M Q8T1 for sequential, RND4K Q1T1 for random. Maker ratings appear only where no independent run exists.
• Specs: the datasheet or product page of each maker, fetched 25 October 2026. Where Amazon copy disagreed (the BAR Plus listing quotes the 64GB read figure), the datasheet won.
• Boot chain: Ventoy 1.1.18 installed with Ventoy2Disk.sh on Ubuntu 26.04.1, a 32 GB disk passed to a QEMU guest as usb-storage on an xHCI controller, OVMF firmware with and without Secure Boot.
• Persistence: Kali 2026.2 live booted through Ventoy with a 4 GiB ext4 persistence image, a file and a package written, the guest powered off and booted again.

Lab numbers that do transfer to real hardware are sizes and write volumes. The Kali 2026.2 live ISO is 5,531,987,968 bytes (5.15 GiB), the persistence image is a 4 GiB file, and a first apt session grew it by 334 MB. Those three numbers set the capacity floor and the write load the stick has to survive, so they feed the capacity advice at the end.

1. PNY PRO Elite V3: best stick for Kali persistence

Among the five, the PNY PRO Elite V3 256GB posts the highest random write of any stick in this guide: 80.92 MB/s at 4K Q1T1. The same CrystalDiskMark run measured 863.24 MB/s sequential write. A live Kali session writing package lists and logs spends its time in that 4K pattern, so this stick keeps apt install feeling like a disk rather than a floppy.

PNY rates it at 1000 MB/s read and 800 MB/s write over USB 3.2 Gen 2, in a metal body with a sliding cap and a 0 to 70 °C operating range. The measured 933.95 MB/s read lands within 7% of the rating, which is rare for a thumb drive. Those sequential figures need a 10 Gbps port. On a 5 Gbps USB 3.2 Gen 1 port the link caps sequential read near the BAR Plus figure. Sequential write still lands far above the BAR Plus 66 MB/s, and the 4K random-write lead should hold because small writes rarely approach the link limit, although no Gen 1 run of this stick is published.

• Who it suits: anyone running Kali, Ubuntu or Fedora live with persistence for days at a time, and anyone who rebuilds Ventoy sticks often enough that a 10 second ISO copy matters.
• Skip it if: warranty length matters to you. PNY covers it for 2 years, against 5 years for the Samsung and Kingston and lifetime for the SanDisk. PNY also publishes no dimensions, so check that it fits next to a neighbouring port.

Price band is about $80 for 256GB, sold and shipped by Amazon on the day we checked. Check the PNY PRO Elite V3 256GB price on Amazon.

2. Samsung BAR Plus: best value Ventoy stick

On the independent run, the Samsung BAR Plus 128GB measured 409.64 MB/s sequential read, 66.29 MB/s sequential write and 26.92 MB/s 4K random write. For a Ventoy stick that mostly boots installers, that read figure is what you feel, and the stick costs about half as much as the PNY. Per gigabyte the two cost the same, because the PNY doubles the capacity, so the saving is in the entry price, not the value per GB.

Capacity changes the write speed on this model, and the Amazon listing does not tell you. The 2024 Samsung datasheet rates the 128GB at 400 MB/s read and 60 MB/s write, the 256GB and 512GB at 400 and 110 MB/s, and the 64GB at 300 and 30 MB/s. Writing a 5.15 GiB Kali ISO plus a 4 GiB persistence image takes about 2.5 minutes on the 128GB at its measured write speed. If you plan to rebuild the stick weekly, the 256GB is the better buy.

• Who it suits: a general multiboot stick holding Ubuntu, Fedora, Kali, Windows and a rescue ISO, with light persistence use.
• Skip it if: you live in a persistent Kali session. At 26.92 MB/s random write it is a third of the PNY, and its rated operating range stops at 60 °C against 70 °C on the PNY.

Samsung adds a 5-year limited warranty plus water, shock, magnet and X-ray ratings. The 128GB sits at about $40. See the Samsung BAR Plus 128GB on Amazon.

3. SanDisk Extreme PRO USB-C: for laptops with only USB-C

SanDisk rates the Extreme PRO with USB-C (SDCZ890) at 1000 MB/s read and 900 MB/s write over USB 3.2 Gen 2, the same rating on every capacity from 256GB to 2TB. It is the pick when the machine you rescue has no USB-A port, which describes a growing share of current laptops.

We could not find an independent benchmark of this USB-C model. The ssd-tester pages titled Extreme PRO cover the older SDCZ880 USB-A drive, rated at 420/380 MB/s, so treat this row as maker figures until someone runs it. SanDisk lists Windows, macOS and Android as supported and does not list Linux, which matters little for a boot stick because the firmware and the kernel on the ISO do the talking.

• Who it suits: USB-C-only laptops, and anyone who wants a lifetime limited warranty on the boot stick.
• Skip it if: your desktops and servers are USB-A. You would carry an adapter for every boot, and the PNY gives measured, not rated, numbers for about the same money.

At about $76 for 256GB it costs a few dollars less than the PNY. Check the SanDisk Extreme PRO USB-C 256GB on Amazon.

4. Kingston DataTraveler Exodia: budget installer stick

For about $26, the Kingston DataTraveler Exodia 256GB is the cheapest way to carry every installer you own. Kingston publishes no MB/s figure for it, and the independent run explains why: 109.11 MB/s sequential read, 20.75 MB/s sequential write and 2.23 MB/s 4K random write.

Booting is fine: at 109 MB/s the Kali ISO streams in under a minute. Writing is the problem. Filling it with a Kali ISO and a 4 GiB persistence image takes about 7 minutes 54 seconds at the measured 20.75 MB/s. At 2.23 MB/s random write, a persistent session stalls on every package install. Treat it as read-mostly installer media.

• Who it suits: a drawer stick with Windows, Ubuntu and Kali installers, written once and booted many times.
• Skip it if: you want persistence, or you rewrite the stick often. The 36x random-write gap to the PNY is the reason we would not run a persistent session from it.

Kingston backs it with a 5-year warranty and a snap-on cap with a coloured keyring loop. See the Kingston DataTraveler Exodia 256GB on Amazon.

5. IODD ST400: ISO files as a real optical drive

Unlike the sticks, the IODD ST400 is a 2.5-inch SATA enclosure with a screen and a keypad. It presents any ISO file on its drive as a virtual optical drive, plus up to three fixed-size VHD files as virtual hard disks. The firmware sees a CD drive, so there is no Ventoy boot loader in the chain and nothing to enroll in MOK.

That makes it the tool for machines that refuse Ventoy: locked-down corporate laptops where you cannot enroll a key, old servers that boot reliably only from optical media, and installs that need the signed boot path of the vendor. The IODD shop page is candid about the limit. It tells buyers to install Legacy through the ISO drive and UEFI through a VHD depending on the situation, so UEFI-only machines may need the VHD route.

• Who it suits: technicians installing on many different machines, and anyone who wants an encrypted (AES-256-XTS), write-protectable ISO library. The IODD wiki gives a PIN of 4 to 38 digits, and the product page quotes up to 76 digits counting a second password.
• Skip it if: you only boot your own hardware. Ventoy on a $40 stick covers that, and the ST400 adds an SSD to the cost because the enclosure ships empty.

Its quirks are documented. Each folder holds at most 32 items, and an ISO split into more than 24 fragments refuses to mount with a DEFRAG error. TRIM and UAS are not supported, and an independent review reports throughput capped near 250 MB/s at SATA II speed. Format the drive exFAT or NTFS rather than FAT32, because the 4 GB file limit of FAT32 is smaller than the 5.15 GiB Kali live ISO.

Expect to pay about $114 for the enclosure before the SSD. Check the IODD ST400 price on Amazon.

Step 1: Install Ventoy on the stick

Ventoy writes a 32 MB EFI partition and gives the rest of the stick to an exFAT data partition, so ISO files of any size copy straight onto it. The steps below are the ones run in the lab; our longer Ventoy multi-boot USB guide covers the GUI and Windows installer. First fetch the latest Linux release:

VTOY_VER=$(curl -s https://api.github.com/repos/ventoy/Ventoy/releases/latest | grep '"tag_name"' | cut -d '"' -f 4 | sed 's/^v//')
echo "$VTOY_VER"

On the lab box the API returned the current release:

1.1.18

Download and unpack the tarball with that version:

curl -LO "https://github.com/ventoy/Ventoy/releases/download/v${VTOY_VER}/ventoy-${VTOY_VER}-linux.tar.gz"
tar xzf "ventoy-${VTOY_VER}-linux.tar.gz"
cd "ventoy-${VTOY_VER}"

Find the stick before you touch it. Ventoy wipes the whole device, so check the size, the model and that the transport column says usb:

lsblk -o NAME,SIZE,MODEL,TRAN

Set the device once, to the disk that lsblk listed with TRAN set to usb. On a SATA desktop /dev/sda is usually the system disk, so replace sdX with your stick; the lab disk was /dev/sda. Every command that writes to the stick below uses this variable:

USB_DEV=/dev/sdX

A new stick deserves one destructive check before anything goes on it, and f3probe has no confirmation prompt, so confirm the variable first. Counterfeit sticks report more capacity than their flash holds, and f3probe finds that by writing and reading test blocks spread across the device. Unmount any partition the desktop auto-mounted from the stick, then install f3 and probe it, which erases it:

sudo umount "${USB_DEV}"?* 2>/dev/null
sudo apt install -y f3
sudo f3probe --destructive --time-ops "$USB_DEV"

The lab ran it against a 2 GB loop device, so the sizes below are that device. A genuine stick reports its announced size as the usable size, while a fake one reports a usable size far below the announced one and names the counterfeit type:

Good news: The device `/dev/loop0' is the real thing

Device geometry:
	         *Usable* size: 2.00 GB (4194304 blocks)
	        Announced size: 2.00 GB (4194304 blocks)
	                Module: 2.00 GB (2^31 Bytes)
	Approximate cache size: 0.00 Byte (0 blocks), need-reset=no
	   Physical block size: 512.00 Byte (2^9 Bytes)

Probe time: 13.16s
 Operation: total time / count = avg time
      Read: 29.0ms / 4811 = 6us
     Write: 12.92s / 2097217 = 6us
     Reset: 0us / 1 = 0us

The probe took 13 seconds on the lab device and takes minutes on a real stick. If it reports bad news (a counterfeit type, a damaged device or a usable size below the announced size), return the stick; the f3write and f3read pair from the same package gives a slower full-coverage check.

Install Ventoy next. The script prints the disk, model and size, then asks twice; answer y only after those three lines match your stick:

sudo sh Ventoy2Disk.sh -i "$USB_DEV"

After the install, two partitions remain: an exFAT data partition labelled Ventoy and the 32 MB VTOYEFI partition:

The model line reads QEMU HARDDISK because the lab used a virtual disk; on a real stick it shows the vendor string. MBR is the default because it is the only layout that also boots legacy BIOS machines. Add -g for GPT, and -r 4096 to reserve 4 GiB at the end of the stick for a separate partition.

Step 2: Copy the Kali and Ubuntu ISOs

The Kali live ISO is published as a torrent only. On 25 October 2026 the release folders on cdimage.kali.org listed kali-linux-2026.2-live-amd64.iso.torrent and no direct ISO, and direct requests for the plain file on several mirrors returned 404. A torrent client verifies every piece against the hashes in the torrent, so the download is checked as it arrives:

sudo apt install -y aria2
KALI_REL=2026.2  # pin: the live ISO is torrent-only, take the release listed on https://www.kali.org/get-kali/
curl -LO "https://cdimage.kali.org/kali-${KALI_REL}/kali-linux-${KALI_REL}-live-amd64.iso.torrent"
aria2c --seed-time=0 "kali-linux-${KALI_REL}-live-amd64.iso.torrent"

Once peers connected, the lab pulled the 5.15 GiB image at about 19 MiB/s. Check it against the published checksum list before it goes on the stick:

curl -sL -o SHA256SUMS "https://cdimage.kali.org/kali-${KALI_REL}/SHA256SUMS"
grep " kali-linux-${KALI_REL}-live-amd64.iso$" SHA256SUMS | sha256sum -c

The lab copy matched the hash Kali publishes:

kali-linux-2026.2-live-amd64.iso: OK

Note the -L: the checksum URL answers with a redirect, and without it curl saves an empty file that sha256sum rejects. This proves the download is intact, not who published it; Kali also ships SHA256SUMS.gpg next to it for a signature check. Mount the Ventoy partition and copy the ISO onto it, then flush the write cache before you go further:

sudo mkdir -p /mnt/ventoy
sudo mount "${USB_DEV}1" /mnt/ventoy
sudo cp "kali-linux-${KALI_REL}-live-amd64.iso" /mnt/ventoy/
sync

Any other ISO goes in the same way; the lab stick also carried ubuntu-26.04.1-live-server-amd64.iso (2.73 GiB), the image our Ubuntu 26.04 install guide walks through. Ventoy lists every ISO it finds when the stick boots:

Ventoy needs no regeneration step after a copy, which is the whole point of it: add or delete ISO files and the menu follows on the next boot.

Step 3: Add a Kali persistence image

Kali keeps changes in an ext4 filesystem labelled persistence that contains a persistence.conf with the line / union. The Ventoy persistence plugin builds that as a file instead of a partition, so the stick stays a plain Ventoy stick. Create the folders and a 4 GiB image from the Ventoy directory:

sudo mkdir -p /mnt/ventoy/persistence /mnt/ventoy/ventoy
sudo sh CreatePersistentImg.sh -s 4096 -l persistence -c persistence.conf -o /mnt/ventoy/persistence/kali-persistence.dat

Point Ventoy at the image by creating its plugin file:

sudo vim /mnt/ventoy/ventoy/ventoy.json

Add this configuration, with the ISO name matching the file you copied, because Ventoy matches the path exactly:

{
    "persistence": [
        {
            "image": "/kali-linux-2026.2-live-amd64.iso",
            "backend": "/persistence/kali-persistence.dat",
            "autosel": 1
        }
    ]
}

The script writes the full 4 GiB with dd before it formats the file, and the lab run below shows that plus the plugin file as written to the stick:

That 4 GiB write is where a slow stick first costs you time: 410 MB/s on the lab disk, but about 3.5 minutes at the measured 20.75 MB/s of the Kingston. Unmount cleanly before you pull the stick. A desktop session may also have mounted the partition under /media/$USER/Ventoy, so eject that one from the file manager too:

sudo umount /mnt/ventoy

With autosel set to 1, Ventoy picks the first backend without asking, so the persistence prompt never appears. Leave it out if you keep several images for one ISO.

Step 4: Boot Kali with persistence and check it

Select the Kali ISO in the Ventoy menu, choose Boot in normal mode, then pick the persistence entry in the Kali menu. Ventoy only attaches the image; Kali mounts it only when booted with this entry:

Once the desktop is up, open a terminal and check what the root filesystem sits on:

findmnt -o TARGET,SOURCE,FSTYPE -t ext4,overlay

Root is an overlay, and its writable layer is the ext4 image that Ventoy exposed as /dev/mapper/vtoy_persistent:

Next we wrote a test file, ran sudo apt-get update and installed tree. Used space in the image went from 29 MB after the first boot to 363 MB, so one package-list refresh and one small package grew it by 334 MB. Mounted on the host afterwards, the image held 245 MB under rw/var/lib, where apt keeps its package lists, and 98 MB under rw/var/cache, where apt keeps its package cache. The lists themselves are a few large files written mostly in sequence, so sequential write sets how long that refresh takes. Random write is our inference for the rest of a persistent session: dpkg status updates, logs and desktop settings are small files synced one at a time, and that is the pattern a 2.23 MB/s stick handles worst.

After a full power-off and a second boot with the same entry, the file and the package were still there:

A 4 GiB image held one session with 3,366 MB to spare, but an image fills quickly once you install tool sets. The ExtendPersistentImg.sh script in the Ventoy folder grows it later, and the stick needs free space for that, which is one more reason to buy 128GB or more.

Warning: “Conflicting distribution: file:/run/live/medium kali-last-snapshot Release”

The live session printed this during apt-get update: W: Conflicting distribution: file:/run/live/medium kali-last-snapshot Release (expected kali-last-snapshot but got kali-rolling). It refers to the package source on the ISO itself, and in our run it was a warning only: the update completed and tree installed and survived the reboot. If you keep a persistent Kali for long, our guide to Kali repositories in sources.list shows the standard network entry.

Step 5: Clear the Secure Boot Security Violation

On a machine with Secure Boot on and the Microsoft keys enrolled, the first boot of a fresh Ventoy 1.1.18 stick stopped at a blue shim screen before the menu:

Ventoy is signed through a third-party shim, and its own loader is trusted only after you add the Ventoy key to the Machine Owner Key list. The Ventoy Secure Boot page also notes that versions 1.1.13 and later need a new key for the UEFI CA 2023 change, so a stick updated from an older release asks again. The sequence that worked in the lab:

1. Press Enter on the error, then any key at Press any key to perform MOK management within its 10 second countdown.
2. Choose Enroll key from disk, then the VTOYEFI volume.
3. Select ENROLL_THIS_KEY_IN_MOKMANAGER.cer, then Continue and Yes.
4. Choose Reboot. The Ventoy menu appears and stays reachable with Secure Boot on.

The certificate sits at the top of the VTOYEFI partition, next to the Ventoy boot folders:

Enrollment is per machine, not per stick. That is the trade-off against the IODD, which needs no enrollment, so a locked-down laptop where you cannot reach MokManager is a job for the IODD. If a Windows or firmware update blocks Ventoy with Verifying shim SBAT data failed: Security Policy Violation instead, the first thing to try is the latest release: download it as in Step 1 and update the stick from that folder with sudo sh Ventoy2Disk.sh -u "$USB_DEV", which keeps your ISO files. The Ventoy issue tracker traced that message to shims revoked by the August 2024 Windows update; the issue is still open, and reports there are mixed on which builds fix it.

What to check before buying a boot stick

Five properties decide whether a stick works well for Ventoy and Linux installers, and the box advertises only one of them:

• 4K random write: the number for persistence. Look for an independent CrystalDiskMark RND4K Q1T1 result; as our rule of thumb, 25 MB/s and up is usable for persistence and under 5 MB/s is installer-only.
• Write speed by capacity: the Samsung BAR Plus 128GB writes at half the rate of the 256GB. Read the datasheet table, not the Amazon headline.
• Capacity floor: Microsoft and Kali both ask for 8 GB minimum. Our lab stick held Kali, Ubuntu server and a 4 GiB image in 11.9 GiB. That makes 32 GB the practical floor, and 128 GB leaves room for Windows and a rescue ISO.
• Port generation: 1000 MB/s ratings need a 10 Gbps USB 3.2 Gen 2 port. A 5 Gbps port caps sequential read and write. Random write should be largely unaffected, because 4K Q1T1 is limited by latency rather than the link. No Gen 1 run of these sticks is published, though.
• Warranty: 2 years on the PNY, 5 years on the Samsung and Kingston, lifetime limited on the SanDisk. A boot stick that also holds persistence wears faster than an installer stick.

Counterfeits are the other risk. A fake stick reports a larger capacity than its flash. The Ventoy FAQ names a fake or faulty stick as the first cause of a boot that drops to a GRUB shell. Buy from listings sold by Amazon or the maker, and probe a new stick with f3 in Step 1, before the Ventoy install. A checksum of one ISO read back right after copying proves little, because the data may still come from the page cache and a fake stick stores the first few gigabytes correctly. The same advice runs through our Unraid flash drive guide, where a counterfeit also breaks the license.

Write time for a full Kali stick, per drive

Loading a Kali stick means writing the 5,531,987,968-byte ISO and the 4,294,967,296-byte persistence image, 9,827 MB together. Dividing that by the sequential write of each drive gives the time you wait every time you rebuild it:

Drive	Seq. write used	Kali ISO	4 GiB persistence image	Both
PNY PRO Elite V3 256GB	863.24 MB/s measured	6.4 s	5.0 s	11.4 s
SanDisk Extreme PRO USB-C 256GB	900 MB/s rated	6.1 s	4.8 s	10.9 s
IODD ST400 + SATA SSD	about 250 MB/s (review)	22.1 s	not used (no Ventoy persistence)	22.1 s
Samsung BAR Plus 128GB	66.29 MB/s measured	83.5 s	64.8 s	2 min 28 s
Kingston DataTraveler Exodia 256GB	20.75 MB/s measured	4 min 27 s	3 min 27 s	7 min 54 s

Treat these as calculations from the cited sequential rates, not timings on the sticks. The IODD row skips the persistence file because the ST400 presents the ISO as an optical drive with no Ventoy plugin. Real copies run a little slower once the file system and cache flush are added. The spread is the point: the same rebuild takes 11 seconds on the PNY and almost 8 minutes on the Kingston, and the random-write gap behind persistence is wider still. For a stick you boot Kali from every week, buy on random write and treat the read speed on the packaging as a tie-breaker. If the stick is for one-off installs such as the Kali install walkthrough, the Samsung or even the Kingston does the job.