Features ›

The editor

Open a file on a server, change it, save it. No download folder, no re-upload step, and no second copy to keep track of.

The file, where it lives

A text file on any supported service opens as a tab inside its connection and saves back to the same place. The source bar says where it came from (SFTP, S3, a local folder) and the status bar shows the language, encoding and line endings it was read with.

Syntax highlighting for 36 languages, from a scanner that carries state across lines, so block comments, template strings and fenced code stay correct
A keystroke re-scans one line rather than the whole file, so large files stay responsive
Find and replace, go to line, auto-indent and bracket pairing
Images open too, recognised by their bytes rather than their name

The editor with cart.js open over SFTP, syntax highlighted, and four documents from the same server in the tab strip

Saves the way each service allows

Most tools download a file, let you edit a copy, and upload it back with their fingers crossed. Hydra saves using the mechanism each service actually supports, and says so when it cannot do better.

SFTP replaces the file through a posix rename
Amazon S3 writes with an If-Match precondition and keeps the object's metadata
FTP has to delete first, and Hydra tells you before it does
Local files use a coordinated atomic replace, with permissions restored

Find in the editor: three matches for subtotal highlighted in cart.js

Nothing lost, nothing changed by accident

Encoding and line endings are detected and preserved, so a one-character edit in a Windows (CRLF) file produces a one-line diff, not a whole-file one.

Unsaved edits are mirrored to disk as you type. If Hydra quits unexpectedly, they come back the next time you open the file, with a diff against what the server holds now, and nothing is ever uploaded without an explicit save.

Try it on your own servers

Fourteen days, everything unlocked, no account required.

Download for macOS