Web servers, browsed like a drive
A lot of files live behind a plain directory listing: a release mirror, a research archive, a colleague's nginx box, an open directory you found. The usual workflow is clicking through bare HTML and saving files one by one. Varv turns that listing into a normal drive: navigate folders, preview files, download whole trees, drag anything straight out.
The servers you actually meet
Apache's mod_autoindex, nginx (including its JSON listings), IIS, lighttpd and Caddy all work out of the box, plus the generic index tables many mirrors use. If a page is not a real directory listing, Varv tells you clearly instead of guessing at it.
Mirror it before it disappears
The real power move: point Varv at a public release archive or an open directory worth keeping, select what matters or the whole tree, and pull it in one go. When the site eventually goes offline, you still have everything. The mirror does not have to land on your disk either: download straight into one of your other connections, so a web archive can flow directly into an S3 bucket or onto an FTP server.
The same queue as everything else
Downloads run through the same verified transfer queue as every other connection: exact file sizes, resume, whole folders at once, and drag straight out. Zip archives on the server open in place, no download first.
Password protected works too
Listings behind HTTP Basic auth work like any other connection: enter the password once and it lives in your system's keychain, only ever sent to that server.
Make anything read only
Web listings are read only by nature. If you want that same safety elsewhere, mark any bucket or server connection read only and nothing on it can be changed, even by accident. Handy when you browse production data all day.
Every file source, one client
Buckets, file servers and now plain web listings, all in the same tabs with the same queue. Varv treats them all like folders.
Get notified at launch