# Matchbox request - socials safety grids

**URL:** <https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123>\
**Category:** Matchbox\
**Created:** [June 30, 2025, 4:57pm UTC](https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123 "2025-06-30T16:57:18Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Epoulson](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/epoulson/32/2207_2.png) [@Epoulson](https://forum.logik.tv/u/Epoulson)\
**Post date:** [June 30, 2025, 4:57pm UTC](https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123/1 "2025-06-30T16:57:18Z")

</div>

Hi all,

Could one of the matchbox wizards out there make a matchbox that has all the socials grids in it that you could cycle through or is it a pain in the arse to keep updated and that’s why there isn’t one?

---

<div class="post-metadata">

**Author:** ![philm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/philm/32/9286_2.png) [@philm](https://forum.logik.tv/u/philm)\
**Post date:** [June 30, 2025, 5:32pm UTC](https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123/2 "2025-06-30T17:32:38Z")

</div>

provide all of the specifications and you helped that developer from having to spend precious time trawling for details.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [June 30, 2025, 6:09pm UTC](https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123/3 "2025-06-30T18:09:21Z")

</div>

They change frequently, or are often non-existant. We have the tools to create them ourselves. As Phil noted, the time intensive part is finding the proper specs.

---

<div class="post-metadata">

**Author:** ![philm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/philm/32/9286_2.png) [@philm](https://forum.logik.tv/u/philm)\
**Post date:** [June 30, 2025, 6:36pm UTC](https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123/4 "2025-06-30T18:36:12Z")

</div>

i expect that all you need is a way to parse XML or json, but the endless misery of finding the specifications is a Sisyphean task, best left to someone who has time to burn.

---

<div class="post-metadata">

**Author:** ![Epoulson](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/epoulson/32/2207_2.png) [@Epoulson](https://forum.logik.tv/u/Epoulson)\
**Post date:** [June 30, 2025, 7:02pm UTC](https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123/5 "2025-06-30T19:02:12Z")

</div>

I thought these would be the answers! Just thought I’d take a punt. I keep forgetting to collect/save built overlays (I freelance at a few different places). Like you guys say the everchanging spec’s are the root of the problem.

thanks anyway

---

<div class="post-metadata">

**Author:** ![bryanb](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/bryanb/32/136_2.png) [@bryanb](https://forum.logik.tv/u/bryanb)\
**Post date:** [July 1, 2025, 1:04am UTC](https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123/6 "2025-07-01T01:04:09Z")

</div>

I see Instagram and tiktok standards changing so often… I make the client provide the safe guides.

---

<div class="post-metadata">

**Author:** ![julioleon](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/julioleon/32/14482_2.png) [@julioleon](https://forum.logik.tv/u/julioleon)\
**Post date:** [July 1, 2025, 10:10pm UTC](https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123/7 "2025-07-01T22:10:57Z")

</div>

You can always do your own presets:

 ![Screenshot 2025-07-01 at 4.09.38 p.m.](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/4/471a89bfc85882b831ec53d93cc66c574acc5534.jpeg)

---

<div class="post-metadata">

**Author:** ![hBomb42](https://avatars.discourse-cdn.com/v4/letter/h/bbce88/32.png) [@hBomb42](https://forum.logik.tv/u/hBomb42)\
**Post date:** [July 1, 2025, 10:19pm UTC](https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123/8 "2025-07-01T22:19:08Z")

</div>

They look like this now, though. Seems tough to do with the overlays panel.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/6/6bfae02c1d3b752baecc5537e52632c8c81500f0.jpeg)

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [July 2, 2025, 12:27am UTC](https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123/9 "2025-07-02T00:27:14Z")

</div>

Every time I follow one of those the client makes me put everything back where it was for the regular 16x9. But, of course, I have to show them first.  
This is the kind that changes so frequently, I make the client provide it.

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [July 4, 2025, 9:24am UTC](https://forum.logik.tv/t/matchbox-request-socials-safety-grids/13123/10 "2025-07-04T09:24:32Z")

</div>

This shit is so crazy. It is good to be informed but often no one else knows or cares until a corporate client gets a random kick back from their daughter.

As Tim says, most clients don’t want to know 🙉

Just sharing this:

> [@Social Media Safety areas](https://forum.logik.tv/t/social-media-safety-areas/5751):
>
> I honestly never gave it a second though… But apparently due to all those emoji overlays and whatnot… ( i am such a boomer) there are about 4000 different social media safety areas. Now with TV mastering I felt like I was the technician that was responsible for reminding people of the holy title safes but with social media… I never get information to where its to be used only spec is “we need a 9:16 version” … Every platform and post-type has different safety margins, how the hell are we…
