Downloading a file

Use the download action on a file row. Your browser starts the download the way it would from any site — there is no client to install and nothing to configure.

What happens before the bytes move

gettor checks that the file is yours, that your plan has monthly download allowance left, that a parallel-download slot is free, and that the account is in good standing. Only then does the download start.

That token carries no session power. It cannot sign you in, list your library, or reach another file — and it is re-checked on every request, not just the first.

When access changes

Because each request is checked on its own, deleting a file, a takedown, or a disabled account stops outstanding delivery links immediately. The link does not stay valid just because it was issued earlier.

What it counts against

Downloading counts against your monthly downloads-and-streaming allowance. Fetching from peers has no separate monthly quota. Downloading the same file twice counts twice.

Resuming an interrupted download

Downloads support range resume, so a dropped connection continues rather than starting over.

A download that stops partway can pick up where it left off in any modern browser or download manager. You do not lose what already arrived.

Why it works

Every request is validated on its own rather than as part of a session, so the browser can ask for just the remaining byte range using the same link and the delivery host will serve exactly that. Seeking in the player uses the same mechanism.

If the link expired while it was paused

Links are short-lived. If a resume is refused, return to the library and start the download again — the app fetches a fresh link, and your browser or download manager will still resume from where it stopped rather than re-fetching the whole file.