Measured from the platform's own overlay, or labeled as a guide
Threads safe zone
Short answer
Koldflux could not fetch a Threads developer page that gives a safe zone, and the recorded device and hub figures disagree. This page shows the range and offers a conservative envelope rather than presenting one as Threads' own rule.
Key takeaways
- No official Threads safe-zone figure was found in the pages Koldflux reached on 2026-10-03. The developer page it could reach was an API reference, not a UI geometry source.
- The recorded device and hub figures disagree, so this page shows the range and an envelope.
- The envelope is the largest margin either recorded source reports, labeled as not an official specification.
- A thread post and a reply are recorded as sharing the same geometry, so one overlay covers both.
The overlay
One surface, and no official geometry was found for it. The overlay is an envelope from the recorded figures.
Sources disagree · Threads API posts (Meta for Developers) · Last checked 2026-10-03
Recorded values range from 5-6% at the top, 8-18% at the bottom, 0-4% on the left and 0-4% on the right. The overlay is an editing guide, not a platform value.
Sources disagree on these margins, so Koldflux does not publish one platform value. The overlay is a cautious editing guide, not an official number.
Surfaces on this platform
One surface, in conflict: the recorded device figures and the recorded hub figures disagree, and the table below shows the gap on each edge. The overlay takes the larger.
Thread Post
CONFLICT · The recorded sources disagree on threads thread-post, so the range is shown below and the download is a conservative envelope.
- Top
- 6% · 115 px
- Bottom
- 18% · 346 px
- Left
- 4% · 43 px
- Right
- 4% · 43 px
| Reported | Top | Bottom | Left | Right |
|---|---|---|---|---|
| Smallest reported | 5% (96 px) | 8% (154 px) | 0% (0 px) | 0% (0 px) |
| Largest reported | 6% (115 px) | 18% (346 px) | 4% (43 px) | 4% (43 px) |
The overlay below uses the largest figure on each edge, so a design inside it is safe under every figure on record. It is an editing guide, not a platform rule.
Source: Threads API posts (Meta for Developers). Checked 2026-10-03.
What was and was not found, and where
The Threads documentation Koldflux could reference describes the posting API and returned an error when fetched. It is an API reference, listing the fields a post carries and the endpoints that create and read them. An API reference is not a source of interface geometry, because it describes what can be submitted rather than what the app draws.
That distinction is the whole of the sourcing position on this page. Koldflux reached a Threads developer page. The page does not carry a safe zone. Nothing else reached carried one either.
The two figures that are on record therefore both come from measurement rather than from Threads, and they disagree: one gives 6% at the top, 18% at the bottom and nothing at the sides; the other gives 5% at the top, 8% at the bottom and 4% on each side.
The gap at the bottom is the widest part of the disagreement, ten points of height between 8% and 18%. At 1920 px that is the difference between 154 px and 346 px, which is the difference between a caption row and most of a screen.
Using an envelope you cannot verify
An envelope is worth having even when the Threads pages Koldflux reached publish no figure at all, for a reason that has nothing to do with the numbers: it forces a decision about where the subject goes. A 6% top and 18% bottom on a 1080 x 1920 frame is 115 px and 346 px, so the rectangle the overlay draws is 994 px wide and 1,459 px tall.
Check a design against the current app rather than against this page. The interface moves between releases, and a figure recorded once is a record of that release.
If you later reach a Threads page that does carry a figure, that figure replaces everything on this page. This page will not be updated to a number it could not read.
| Edge | Margin | Working | Pixels |
|---|---|---|---|
| Top | 6% | 1920 x 0.06 | 115.2, shown as 115 |
| Bottom | 18% | 1920 x 0.18 | 345.6, shown as 346 |
| Left | 4% | 1080 x 0.04 | 43.2, shown as 43 |
| Right | 4% | 1080 x 0.04 | 43.2, shown as 43 |
| Safe width | 92% | 1080 x 0.92 | 993.6, shown as 994 |
| Safe height | 76% | 1920 x 0.76 | 1,459.2, shown as 1,459 |
Computed from the 1080 x 1920 frame and the recorded margins.
The safe width and height are what is left after the largest margin on each edge is taken off, so 1080 less 43 less 43 is 994 and 1920 less 115 less 346 is 1,459. Both are shown rounded to whole pixels.
Downloads
Thread Post
This is a conservative envelope, not an official specification. The Threads pages Koldflux reached carry no safe zone at all, so the two numbers here are Koldflux records rather than Threads rules. The overlay keeps the larger margin either record reports on each edge, which means a design inside it survives whichever record turns out to be right. The file says so on its face.
Frequently asked questions
What is the Threads safe zone?
No official figure was found in the pages Koldflux could reach. The recorded device and hub sources disagree, so this page offers a conservative envelope, the largest margin any of them reports, labeled as not an official specification.
Does Threads publish a safe zone?
Not in the pages Koldflux reached on 2026-10-03. The developer documentation is an API reference rather than a source of interface geometry, so the overlay here is a recorded envelope.
Can I use the Instagram Reels safe zone for Threads?
Not reliably. Threads shares Instagram's account pipeline but a thread post sits in a different interface from a Reel, so the margins differ. This page uses the Threads row, not the Reels one.
Does a Threads reply need its own overlay?
No. The geometry of a reply is recorded as identical to that of the thread post, so the same overlay covers both surfaces.
Sources
- Meta for Developers: Threads API posts (checked 2026-10-03)
The Threads developer documentation Koldflux reached is an API reference rather than a source of interface geometry, so no Threads figure is quoted here. The overlay is a recorded envelope.