Download route: the path a file leaves by
A download route is the path a file leaves a product by: a website, an app, an interface response. One entry here makes the route the subject of its marking statement rather than the model. As of 2026-09-22.
| The term | Download route |
|---|---|
| What it names | The path by which a file leaves a product |
| What it is not | The model, or the plan the account is on |
| Where the register uses it | One entry's visible-mark value, scoped as written |
Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.
1A statement about a route is narrower than it looks
Videos downloaded from the vendor's own website and app is a sentence about two doors. Every other way of obtaining the same output is neither included nor excluded by it, and the register records the scope rather than generalising to all output from the model.
That restraint looks excessive until another entry demonstrates why it is not: one vendor documents a console that always stamps and an interface that defaults to not stamping, so a route-scoped statement can be true while its generalisation is false.
2Why marking at the download is a natural place to put it
A mark applied when a file leaves catches everything on the way out, regardless of how it was produced, and leaves the generation path untouched. It is also the last moment at which a vendor controls the file, which makes it the obvious place for a provenance overlay.
It does mean the mark is a property of the exit rather than of the content. A file obtained some other way from the same model is a different case, and on this entry nothing is published about it.
3What the register can and cannot record
The scope as written, in the applies-to note beside the value, and the fact that the entry's documents describe no other route. Not an inference about those routes, and not a conclusion that they produce unmarked files.
A reader integrating such a model needs the sentence and its edge. The cell gives both, which is the whole reason values here repeat vendor wording rather than being translated into a cleaner yes or no.
Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the user toggle column, source documents. Nearby terms: burned-in mark, corner stamp, full-frame mark.