// Docs

Where the files come from

Archives, remote servers, Git revisions, snapshots and the clipboard, each as one side of a comparison.

A side of a comparison does not have to be a folder on a disk. The path bar above each side says what that side is and can switch it: local, an archive, a remote connection, a Git revision, a snapshot or the clipboard. Everything downstream — the rules, the filters, the file operations, the reports — works the same whichever it is.

Archives

An archive opens as a folder, and the files inside are compared without being extracted first. Read on every platform, with no system library behind them: zip, tar (gzip, bzip2, xz, zstd, lzip, lzma), 7z, single compressed files, rar, iso, cab, deb, rpm, cpio, wim/esd and chm. The Windows build can also use Total Commander packer plug-ins for anything else.

zip, tar, tar.gz and 7z are also written back: copying a file into an archive, deleting one or editing one collects the changes, and writing them out rewrites the archive beside the original, renames the original to .bak and moves the new one into place. Up to that last moment it can be cancelled, and the original is untouched.

Whether an archive is compared as one file or expanded as a folder is a rule (session rules › Other, and Preferences › Archive types), so a .jar can be a folder in one session and a file in another.

Remote

SFTP, FTP/FTPS, S3, WebDAV and Subversion are all set up as named connections (Home › Remote): a form each, with a “Test” that says what the server answered. Passwords and keys go to the system keychain, never into the session file; SFTP takes a password, a private key, keyboard-interactive or an ssh agent, and an unknown host key is shown and asked about rather than accepted quietly. The Windows build adds portable devices (phones, cameras, media players) through Windows Portable Devices.

What they share matters more than what sets them apart: one read cache, uploads to a temporary name so a half-written file never takes the real one’s place, resume after a dropped connection, retries, cancellation, and a connection log you can read when something is odd. A remote folder is listed as you unfold it, so a comparison starts at the root instead of walking the whole tree — except where a rule needs the whole tree (a content filter, the flat view, “Expand all”), when the app says so while it reads.

Git revisions

One side can be a repository at a revision, or its working tree. Trees are read one directory at a time, so opening a revision costs what you look at rather than the size of the repository, and two revisions of the same file are told apart by their Git ids without reading anything. What Git does not store is reported honestly: a revision has no per-file timestamps, so time is not a criterion there; filters are not applied, so an LFS file reads as its pointer; a submodule is the one line git diff shows, with the commit it records.

Snapshots

A snapshot is one file holding the names, sizes, times, attributes and link targets of a whole tree — optionally with CRCs and executables’ version information, never contents. It is written in the background and can be gzipped; it is written beside its destination and renamed into place, so a cancelled save leaves nothing behind.

Compare a folder with a snapshot of itself from last week and the comparison says what moved, grew or vanished. Because there are no contents, the comparison can only use size, time, hash and version information, and the session says so in a notice rather than pretending otherwise.

The clipboard

Copy two pieces of text and compare them without saving them as files. On Windows, GeeCompare can also take the clipboard at login, so a comparison started from another program finds its content there.

Last updated: 2026-11-22