tiktok-safe-zone-notes 0.1.0__tar.gz

tiktok_safe_zone_notes-0.1.0/PKG-INFO

@@ -0,0 +1,54 @@
+Metadata-Version: 2.4
+Name: tiktok-safe-zone-notes
+Version: 0.1.0
+Summary: Notes on the TikTok Safe Zone: Why the Numbers Matter More Than the Frame
+Author: andy
+License: MIT
+Project-URL: Homepage, https://seedance-2ai.org/tools/tiktok-safe-zone
+Project-URL: TikTok Safe Zone, https://seedance-2ai.org/tools/tiktok-safe-zone
+Keywords: tiktok,video,safe-zone,vertical-video
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+
+# Notes on the TikTok Safe Zone: Why the Numbers Matter More Than the Frame
+
+Every guide to vertical video eventually arrives at a diagram with a rectangle drawn over a phone screen, and every diagram disagrees slightly with the next one. The disagreement is not carelessness. It comes from the fact that almost nobody publishing the numbers says where they came from. Reading the documentation behind one of the checkers, my impression is that the useful distinction is between a measurement taken from a platform's own specification and a guess made from screenshots, and that most safe zone advice is the second kind wearing the confidence of the first.
+
+## Where the published numbers come from
+
+TikTok publishes a safe zone file for ads, and the checker on GenWorldAI works from that file, dated April 2025, and notes when it was last verified. On a 1080 by 1920 video the zone starts 240 px below the top and ends 660 px above the bottom, with 120 px at each side. A buttons column runs 300 px wide on the right from y 840 downward. Those are six numbers, and they are enough to draw the whole thing. The reason I find this worth noting is the honesty of the framing: the same page states plainly that the platforms publish numbers only for ads, and that regular posts have no equivalent document. The ad zone therefore functions as a conservative guide rather than a promise.
+
+That distinction shapes how I read every other safe zone guide. If the numbers cannot be traced to a platform document, they are an observation of one app on one phone on one day, which is still useful but is a different kind of claim.
+
+## The frame is not the composition
+
+The concept that took me longest to internalise is that the 1080 by 1920 canvas and the visible area are two separate things. A caption placed twenty pixels from the top edge is not cropped; it is simply drawn over. The app paints its own interface on top of the video, and what the interface covers depends on which screen the viewer is on: the feed, the profile grid, a search result, a share sheet. This is why the checker maps two conditions rather than one. Red marks what sits under the app's buttons and text. Blue marks what may be cut off on some phones. Nothing in that scheme is about the video's quality.
+
+A second principle follows from it. The covered area is not a fixed shape across platforms. The same vertical clip shown on TikTok, Reels and Shorts has three different interfaces over it, and the checker shows all three at once for that reason. Designing for the narrowest visible area is the only approach that survives being posted in more than one place, and the layout sketch it provides is explicitly labelled an illustration rather than a rendering of any particular app, which is the right level of ambition for a drawing of that kind.
+
+## What the tool actually asks of you
+
+The practice is three steps. Drop an MP4, MOV, PNG or JPG, or start from the empty 9:16 frame and scrub through a clip with the zone drawn on top. Drag a box around each caption, logo or face, and the tool reports whether that object is safe on every platform. Download a transparent template at 1080 by 1920 or 2160 by 3840, place it on the top track in CapCut, Premiere or DaVinci, or as the top layer in Canva, and hide it before export.
+
+The marking step is where the method earns its keep, because it converts an unhelpful judgement into arithmetic. When a caption is covered, the tool gives the exact move that makes it safe: move up 310 px, for instance. The 2160 by 3840 template matters for the same reason, since 1080 by 1920 is half the published figure and the zone has to be scaled with it. Everything runs in the browser, nothing is uploaded, and no account is needed, which is the only arrangement I would want for a client's unreleased footage. For teams that storyboard vertical work before generating anything, a 9:16 storyboard plan is the cheaper place to catch this problem, and GenWorldAI opens its text to video tool at 9:16 for that purpose.
+
+## Where the errors come from
+
+The most common mistake is treating the safe zone as advice about beauty rather than about legibility: nudging a logo slightly downward because it looks better there, then losing it under the caption text on a specific device. The second is checking one frame of a video whose text moves, when the zone applies to every moment and the checker exists to let you scrub through all of them. The third is assuming the aspect ratio carries the composition. A 9:16 export that keeps all its important elements inside a square in the centre will look sparse in an app but will be safe nearly everywhere.
+
+The fourth is subtler. Because no platform publishes numbers for regular posts, people conclude there are no numbers at all and design by feel. The ad file is not the same document as a feed specification, but it is the closest published thing, and building to it costs nothing.
+
+## What I take from all of this
+
+I think of the safe zone as a contract drawn up by the interface rather than by the video. The measurement belongs to the platform, the template is the way of carrying that measurement into an editor, and the marking step is how a creator proves that a particular caption in a particular clip respects it. A [tiktok safe zone](https://seedance-2ai.org/tools/tiktok-safe-zone) overlay is, in that sense, nothing more than the contract made visible while you work.
+
+My reading is that the discipline transfers well beyond the app it was written for. Once a creator has internalised the four margins and the buttons column, the habit of planning for a covered area survives every change the platforms make to their buttons, because the habit is about reserving space rather than memorising coordinates. The numbers are dated; the way of thinking about them is not.
+
+The GenWorldAI checker is a reasonable place to keep that reference, since it shows the zone, the platform differences and the template in one view and states the source of its figures instead of presenting them as eternal. For anyone who has ever exported a vertical clip and found the caption sitting under a username, the three steps are probably the fastest route from guessing to knowing.
+
+## Further reading
+
+Platform safe zone documentation for ads, including TikTok's 2025 auction in-feed file. GenWorldAI's TikTok Safe Zone Checker and Template, which supplies the measurements quoted here and the free templates. Standard editor documentation for CapCut, Premiere, DaVinci Resolve and Canva, for placing an overlay on the top track.

tiktok_safe_zone_notes-0.1.0/README.md

@@ -0,0 +1,39 @@
+# Notes on the TikTok Safe Zone: Why the Numbers Matter More Than the Frame
+
+Every guide to vertical video eventually arrives at a diagram with a rectangle drawn over a phone screen, and every diagram disagrees slightly with the next one. The disagreement is not carelessness. It comes from the fact that almost nobody publishing the numbers says where they came from. Reading the documentation behind one of the checkers, my impression is that the useful distinction is between a measurement taken from a platform's own specification and a guess made from screenshots, and that most safe zone advice is the second kind wearing the confidence of the first.
+
+## Where the published numbers come from
+
+TikTok publishes a safe zone file for ads, and the checker on GenWorldAI works from that file, dated April 2025, and notes when it was last verified. On a 1080 by 1920 video the zone starts 240 px below the top and ends 660 px above the bottom, with 120 px at each side. A buttons column runs 300 px wide on the right from y 840 downward. Those are six numbers, and they are enough to draw the whole thing. The reason I find this worth noting is the honesty of the framing: the same page states plainly that the platforms publish numbers only for ads, and that regular posts have no equivalent document. The ad zone therefore functions as a conservative guide rather than a promise.
+
+That distinction shapes how I read every other safe zone guide. If the numbers cannot be traced to a platform document, they are an observation of one app on one phone on one day, which is still useful but is a different kind of claim.
+
+## The frame is not the composition
+
+The concept that took me longest to internalise is that the 1080 by 1920 canvas and the visible area are two separate things. A caption placed twenty pixels from the top edge is not cropped; it is simply drawn over. The app paints its own interface on top of the video, and what the interface covers depends on which screen the viewer is on: the feed, the profile grid, a search result, a share sheet. This is why the checker maps two conditions rather than one. Red marks what sits under the app's buttons and text. Blue marks what may be cut off on some phones. Nothing in that scheme is about the video's quality.
+
+A second principle follows from it. The covered area is not a fixed shape across platforms. The same vertical clip shown on TikTok, Reels and Shorts has three different interfaces over it, and the checker shows all three at once for that reason. Designing for the narrowest visible area is the only approach that survives being posted in more than one place, and the layout sketch it provides is explicitly labelled an illustration rather than a rendering of any particular app, which is the right level of ambition for a drawing of that kind.
+
+## What the tool actually asks of you
+
+The practice is three steps. Drop an MP4, MOV, PNG or JPG, or start from the empty 9:16 frame and scrub through a clip with the zone drawn on top. Drag a box around each caption, logo or face, and the tool reports whether that object is safe on every platform. Download a transparent template at 1080 by 1920 or 2160 by 3840, place it on the top track in CapCut, Premiere or DaVinci, or as the top layer in Canva, and hide it before export.
+
+The marking step is where the method earns its keep, because it converts an unhelpful judgement into arithmetic. When a caption is covered, the tool gives the exact move that makes it safe: move up 310 px, for instance. The 2160 by 3840 template matters for the same reason, since 1080 by 1920 is half the published figure and the zone has to be scaled with it. Everything runs in the browser, nothing is uploaded, and no account is needed, which is the only arrangement I would want for a client's unreleased footage. For teams that storyboard vertical work before generating anything, a 9:16 storyboard plan is the cheaper place to catch this problem, and GenWorldAI opens its text to video tool at 9:16 for that purpose.
+
+## Where the errors come from
+
+The most common mistake is treating the safe zone as advice about beauty rather than about legibility: nudging a logo slightly downward because it looks better there, then losing it under the caption text on a specific device. The second is checking one frame of a video whose text moves, when the zone applies to every moment and the checker exists to let you scrub through all of them. The third is assuming the aspect ratio carries the composition. A 9:16 export that keeps all its important elements inside a square in the centre will look sparse in an app but will be safe nearly everywhere.
+
+The fourth is subtler. Because no platform publishes numbers for regular posts, people conclude there are no numbers at all and design by feel. The ad file is not the same document as a feed specification, but it is the closest published thing, and building to it costs nothing.
+
+## What I take from all of this
+
+I think of the safe zone as a contract drawn up by the interface rather than by the video. The measurement belongs to the platform, the template is the way of carrying that measurement into an editor, and the marking step is how a creator proves that a particular caption in a particular clip respects it. A [tiktok safe zone](https://seedance-2ai.org/tools/tiktok-safe-zone) overlay is, in that sense, nothing more than the contract made visible while you work.
+
+My reading is that the discipline transfers well beyond the app it was written for. Once a creator has internalised the four margins and the buttons column, the habit of planning for a covered area survives every change the platforms make to their buttons, because the habit is about reserving space rather than memorising coordinates. The numbers are dated; the way of thinking about them is not.
+
+The GenWorldAI checker is a reasonable place to keep that reference, since it shows the zone, the platform differences and the template in one view and states the source of its figures instead of presenting them as eternal. For anyone who has ever exported a vertical clip and found the caption sitting under a username, the three steps are probably the fastest route from guessing to knowing.
+
+## Further reading
+
+Platform safe zone documentation for ads, including TikTok's 2025 auction in-feed file. GenWorldAI's TikTok Safe Zone Checker and Template, which supplies the measurements quoted here and the free templates. Standard editor documentation for CapCut, Premiere, DaVinci Resolve and Canva, for placing an overlay on the top track.

tiktok_safe_zone_notes-0.1.0/pyproject.toml

@@ -0,0 +1,21 @@
+[build-system]
+requires = ["setuptools>=61"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "tiktok-safe-zone-notes"
+version = "0.1.0"
+description = "Notes on the TikTok Safe Zone: Why the Numbers Matter More Than the Frame"
+readme = "README.md"
+requires-python = ">=3.8"
+license = {text = "MIT"}
+authors = [{name = "andy"}]
+keywords = ["tiktok", "video", "safe-zone", "vertical-video"]
+classifiers = [
+  "Programming Language :: Python :: 3",
+  "License :: OSI Approved :: MIT License",
+  "Operating System :: OS Independent",
+]
+[project.urls]
+Homepage = "https://seedance-2ai.org/tools/tiktok-safe-zone"
+"TikTok Safe Zone" = "https://seedance-2ai.org/tools/tiktok-safe-zone"

tiktok_safe_zone_notes-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

tiktok_safe_zone_notes-0.1.0/src/tiktok_safe_zone_notes/__init__.py

@@ -0,0 +1 @@
+# tiktok safe zone notes

tiktok_safe_zone_notes-0.1.0/src/tiktok_safe_zone_notes.egg-info/PKG-INFO

@@ -0,0 +1,54 @@
+Metadata-Version: 2.4
+Name: tiktok-safe-zone-notes
+Version: 0.1.0
+Summary: Notes on the TikTok Safe Zone: Why the Numbers Matter More Than the Frame
+Author: andy
+License: MIT
+Project-URL: Homepage, https://seedance-2ai.org/tools/tiktok-safe-zone
+Project-URL: TikTok Safe Zone, https://seedance-2ai.org/tools/tiktok-safe-zone
+Keywords: tiktok,video,safe-zone,vertical-video
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+
+# Notes on the TikTok Safe Zone: Why the Numbers Matter More Than the Frame
+
+Every guide to vertical video eventually arrives at a diagram with a rectangle drawn over a phone screen, and every diagram disagrees slightly with the next one. The disagreement is not carelessness. It comes from the fact that almost nobody publishing the numbers says where they came from. Reading the documentation behind one of the checkers, my impression is that the useful distinction is between a measurement taken from a platform's own specification and a guess made from screenshots, and that most safe zone advice is the second kind wearing the confidence of the first.
+
+## Where the published numbers come from
+
+TikTok publishes a safe zone file for ads, and the checker on GenWorldAI works from that file, dated April 2025, and notes when it was last verified. On a 1080 by 1920 video the zone starts 240 px below the top and ends 660 px above the bottom, with 120 px at each side. A buttons column runs 300 px wide on the right from y 840 downward. Those are six numbers, and they are enough to draw the whole thing. The reason I find this worth noting is the honesty of the framing: the same page states plainly that the platforms publish numbers only for ads, and that regular posts have no equivalent document. The ad zone therefore functions as a conservative guide rather than a promise.
+
+That distinction shapes how I read every other safe zone guide. If the numbers cannot be traced to a platform document, they are an observation of one app on one phone on one day, which is still useful but is a different kind of claim.
+
+## The frame is not the composition
+
+The concept that took me longest to internalise is that the 1080 by 1920 canvas and the visible area are two separate things. A caption placed twenty pixels from the top edge is not cropped; it is simply drawn over. The app paints its own interface on top of the video, and what the interface covers depends on which screen the viewer is on: the feed, the profile grid, a search result, a share sheet. This is why the checker maps two conditions rather than one. Red marks what sits under the app's buttons and text. Blue marks what may be cut off on some phones. Nothing in that scheme is about the video's quality.
+
+A second principle follows from it. The covered area is not a fixed shape across platforms. The same vertical clip shown on TikTok, Reels and Shorts has three different interfaces over it, and the checker shows all three at once for that reason. Designing for the narrowest visible area is the only approach that survives being posted in more than one place, and the layout sketch it provides is explicitly labelled an illustration rather than a rendering of any particular app, which is the right level of ambition for a drawing of that kind.
+
+## What the tool actually asks of you
+
+The practice is three steps. Drop an MP4, MOV, PNG or JPG, or start from the empty 9:16 frame and scrub through a clip with the zone drawn on top. Drag a box around each caption, logo or face, and the tool reports whether that object is safe on every platform. Download a transparent template at 1080 by 1920 or 2160 by 3840, place it on the top track in CapCut, Premiere or DaVinci, or as the top layer in Canva, and hide it before export.
+
+The marking step is where the method earns its keep, because it converts an unhelpful judgement into arithmetic. When a caption is covered, the tool gives the exact move that makes it safe: move up 310 px, for instance. The 2160 by 3840 template matters for the same reason, since 1080 by 1920 is half the published figure and the zone has to be scaled with it. Everything runs in the browser, nothing is uploaded, and no account is needed, which is the only arrangement I would want for a client's unreleased footage. For teams that storyboard vertical work before generating anything, a 9:16 storyboard plan is the cheaper place to catch this problem, and GenWorldAI opens its text to video tool at 9:16 for that purpose.
+
+## Where the errors come from
+
+The most common mistake is treating the safe zone as advice about beauty rather than about legibility: nudging a logo slightly downward because it looks better there, then losing it under the caption text on a specific device. The second is checking one frame of a video whose text moves, when the zone applies to every moment and the checker exists to let you scrub through all of them. The third is assuming the aspect ratio carries the composition. A 9:16 export that keeps all its important elements inside a square in the centre will look sparse in an app but will be safe nearly everywhere.
+
+The fourth is subtler. Because no platform publishes numbers for regular posts, people conclude there are no numbers at all and design by feel. The ad file is not the same document as a feed specification, but it is the closest published thing, and building to it costs nothing.
+
+## What I take from all of this
+
+I think of the safe zone as a contract drawn up by the interface rather than by the video. The measurement belongs to the platform, the template is the way of carrying that measurement into an editor, and the marking step is how a creator proves that a particular caption in a particular clip respects it. A [tiktok safe zone](https://seedance-2ai.org/tools/tiktok-safe-zone) overlay is, in that sense, nothing more than the contract made visible while you work.
+
+My reading is that the discipline transfers well beyond the app it was written for. Once a creator has internalised the four margins and the buttons column, the habit of planning for a covered area survives every change the platforms make to their buttons, because the habit is about reserving space rather than memorising coordinates. The numbers are dated; the way of thinking about them is not.
+
+The GenWorldAI checker is a reasonable place to keep that reference, since it shows the zone, the platform differences and the template in one view and states the source of its figures instead of presenting them as eternal. For anyone who has ever exported a vertical clip and found the caption sitting under a username, the three steps are probably the fastest route from guessing to knowing.
+
+## Further reading
+
+Platform safe zone documentation for ads, including TikTok's 2025 auction in-feed file. GenWorldAI's TikTok Safe Zone Checker and Template, which supplies the measurements quoted here and the free templates. Standard editor documentation for CapCut, Premiere, DaVinci Resolve and Canva, for placing an overlay on the top track.

tiktok_safe_zone_notes-0.1.0/src/tiktok_safe_zone_notes.egg-info/SOURCES.txt

@@ -0,0 +1,7 @@
+README.md
+pyproject.toml
+src/tiktok_safe_zone_notes/__init__.py
+src/tiktok_safe_zone_notes.egg-info/PKG-INFO
+src/tiktok_safe_zone_notes.egg-info/SOURCES.txt
+src/tiktok_safe_zone_notes.egg-info/dependency_links.txt
+src/tiktok_safe_zone_notes.egg-info/top_level.txt

tiktok_safe_zone_notes-0.1.0/src/tiktok_safe_zone_notes.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

tiktok_safe_zone_notes-0.1.0/src/tiktok_safe_zone_notes.egg-info/top_level.txt

@@ -0,0 +1 @@
+tiktok_safe_zone_notes