Why a mark in a corner is a hostage
A notice rendered into the frame survives whatever the frame survives, and the frame does not survive intact. Platforms crop, pad and recompose, and the region a mark was placed in is not guaranteed to be shown. As of 2026-09-12.
| Operation | Effect on a corner mark |
|---|---|
| A crop to a different aspect ratio | May remove the corner entirely |
| Padding to a taller frame | Keeps it, smaller, further from the edge |
| A platform overlay in the same corner | Obscures it, without removing it |
| A scale to a small player | Keeps it, possibly below legibility |
Inclusion rule. Reframing operations common in vertical and short-form delivery. Order. From most destructive to least.
1Position is a property of the notice, and it is rarely stated
A mark that says nothing about where it sits cannot be reasoned about. One that names a corner can be checked against the safe area of each surface a production publishes to.
Very few vendor pages state a position. It is one of the properties a disclosure aimed at a person actually turns on, and it is among the least documented things in this whole subject.
2Legibility is the other unstated property
Size, opacity and typeface decide whether anybody can read a notice on a phone. A notice rendered small enough satisfies the letter of a claim that a mark exists and nothing else.
Nothing in this record's vendor pages states any of those three. A reader who needs them has to render a file and look, which is one test per tool rather than one per delivery.
3A moving mark answers the crop problem and costs something
A notice that travels across the frame has no single region to remove, so taking it out costs most of the picture or actual work. It is also harder to ignore, which is the point and the complaint.
Whether that is desirable depends on who is delivering. For a platform it is robustness; for a client deliverable it is a problem somebody will ask to have removed.
4Testing the surface, not the export
The useful check is to publish one asset through each surface a production uses and look at what the audience sees. It takes an afternoon and answers the question for every asset that follows.
Reading a vendor page cannot answer it, because the vendor does not control the surface. This is the part of the problem that belongs entirely to whoever is publishing.
Background on mechanism and practice. Nothing here is attributed to a product, and nothing here is a reading of any instrument. The sourced material is on the generator table. Related: Thresholds, Verify the route.