Why bother with guidelines?

• Protects your brand vibe (and copyright).
• Ensures content quality for easier approval later

Think of guidelines as the how-to for clippers to match your style.

‍

To start, here are some frequently used requirements you may want to include in your own brief with quick-win phrasing. Feel free to have your own spin of it!

• Any theme works, but disturbing or explicitly clips will be rejected
• Comments & likes must stay ON
• No AI-generated footage, editing tools are fine, but use existing footage or provided clips
• We reserve the right to reject videos that are entirely off-brand or unrelated

‍

Sample Requirements by Type

Whether you’re a musician, content creator, or event organizer, there are different kinds of content requirements that make sense for you. Here are some examples, think of which of them align with you.

‍

🎸 Musicians / Artists

• Must use the official linked audio track (≥ 90 % volume).

• Any vibe is fine, but keep it PG13

• No mash‑ups, remixes, or unrelated overlays

• Keep visuals engaging & on‑brand

‍

🎮 Content Creators / Streamers

• Grab 15–60 sec highlights (clutch plays, funny fails, big reactions).

• Add provided captions/overlays if any

• Don’t strip out chat hype or add random music

‍

🎤 Event Organizers

• Showcase best moments (crowd energy, performer cameos)

• Use vertical & short layout for social

• Include event name/date if supplied

• Don’t show any brand logo that isn’t ours

‍

🛍️ Brands

• Feature the product clearly 

• Follow branding cues: hashtags, text, angle

• Fun, upbeat tone for social feeds

• No competitor shout‑outs or guideline breaks

‍

Last‑Minute Checklist

1. Did you link all must‑use assets (audio, logos, overlays)? Is the link on read-all?
2. Are deal‑breakers (No NSFW, AI ban, etc.) spelled out?
3. Did you reiterate what content to DO or DON’T do?

‍

With crisp guidelines, our community can turn raw moments into scroll‑stopping shorts in hours. 

If everything looks clean and covered, then you’re good to go! Keep it in the text section of your Content Requirements and move on to the next step.

‍