V-drop support
Something not working, a question before you buy, or a feature you wish it had — we read everything.
Get in touch
Email support@collectivision.net or use the contact form. For a transfer problem, it helps a lot to include your macOS version, the card and reader you were using, and what the app showed when it stopped.
Requirements
macOS 14 (Sonoma) or later, Apple silicon or Intel. Any card reader or drive that mounts as a removable volume. A USB RGB indicator light is optional.
Common questions
V-drop didn't notice my card
V-drop watches for anything that mounts as a removable volume. If the card doesn't appear in Finder either, it's the reader or the card — try a different port or reader first. If Finder sees it and V-drop doesn't, quit and reopen V-drop with the card inserted.
It asks permission for every new card (Mac App Store version)
The App Store build is sandboxed, so macOS requires your consent before an app can read a volume. The first time you insert a given card, V-drop shows a panel already pointed at it — one click on Grant Accessis all it needs. That choice is remembered for that card, so it won't ask again. A new or reformatted card counts as a new card.
My USB light isn't lighting up
V-drop supports blink(1), Luxafor, and generic HID RGB lights. Plug the light in before launching V-drop, then check the Hardware section — a detected light is listed by name. If it's missing, try another USB port or a powered hub; some lights won't enumerate through an unpowered dock. The light is entirely optional — the on-screen indicator shows the same states.
A transfer failed verification
That is the safety net doing its job: V-drop compares a SHA-256 checksum of every file at the destination against the source, and a mismatch means the copy is not trustworthy. Nothing is deleted from your card when this happens. Retry the offload — if the same file fails twice, suspect the card or the reader, and copy that card manually before reusing it.
It says there's not enough space
V-drop checks free space at the destination before it copies anything, so it stops rather than filling a disk halfway. On network volumes the reported free space can be wrong or slow to update; remount the share and try again.
The card didn't eject
Eject only happens once every file handle is closed and the volume is flushed — the green light means it is genuinely safe to pull the card, so V-drop will not fake it. Another app holding a file open (a Finder window, an editor with the card in a project) will block it. Close those and eject from Finder.
SCP/SFTP destinations aren't in my copy
Server destinations ship in the direct-download build today. The Mac App Store build is Finder-destination only for now and adds them in a later update — the sandbox needs an in-process SFTP client rather than the system tools.
More answers in the FAQ · Privacy policy