GateTrue

What each generator documents about marking its output

Crop: cutting away the area a mark sits in

A crop removes area from the edges of a frame. It is the operation a stationary corner mark is vulnerable to, and the reason a vendor publishing motion or extent has told a reader something useful. As of 2026-09-22.

What a crop reaches, and what it leaves behindCropping changes the picture, so it threatens a stationary mark in the region it removes and an in-picture invisible signal, while leaving a container-level manifest completely intact. A moving mark has no single region for a crop to exclude.What does a crop do to this markA stationary corner badgeRemovedIf the region it occupiesfalls outside the newframe. Costs compositiononly.A moving markStill presentNo single region containsit, so one crop cannotexclude it across a clip.An attached manifestUntouchedIt lives in the container,which a crop does notreach at all.Size decides how much framing a crop costs, and size is unpublished
Fig. 1 A crop and a re-encode threaten opposite layers. A file through both has lost whichever was vulnerable to each.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termCrop
What it namesRemoving area from the edges of a frame
What it is notScaling, which keeps the whole frame at a different size
Where the register uses itThe readings that publish a mark's geometry

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.

1The cheapest attack, and the one geometry answers

Cropping costs nothing but composition. Nobody needs a tool beyond an editor, and the result is a clean frame at a slightly tighter framing. That is why the geometry of a mark matters more than its existence: a corner badge can be removed this way and a mark covering the picture cannot.

A mark that travels defeats it differently. No single crop excludes a moving mark for the whole clip, so the operation stops being a one-step fix and starts requiring per-shot work. One adjective on one page in this register says that.

2Why a crop leaves the other layers alone

It changes the picture, so anything attached to the container is untouched: a manifest survives a crop intact, and a metadata block does not notice. An in-picture invisible signal is the layer at risk instead, which is why schemes name cropping among the transformations they aim to survive.

So a crop and a re-encode threaten opposite layers, and a file that has been through both has lost whichever layers were vulnerable to each. Neither operation is hostile; both are things that happen to video.

3What the register can say about it

Which entries publish a geometry, and what each one implies about a crop. Nothing about outcomes, because that would require running files, and nothing about size, which is unpublished everywhere and is what decides how much framing a crop costs.

A reader who needs to know whether a particular crop clears a particular mark is looking for a measurement no page in this register contains. The most any entry supplies is a corner, a motion, or an extent.

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 machine-readable column, what survives an export. Nearby terms: reframe, lossy compression, frame-rate change.