Meta GenAI ad tools: the input licence and your uploaded clip

Meta's Ad Creative Generative AI Terms grant Meta a perpetual licence to Inputs. Which clips are Inputs, and how to render a separate copy for those tools.

4 min readSume
All posts

Under Meta's Ad Creative Generative AI Terms, using the Ad Creative AIs grants Meta a perpetual, worldwide, non-exclusive, fully paid, royalty-free licence to use any Input for the purposes in the terms. A clip is an Input only when you give it to one of those features. Decide per clip before you do, and render a separate working copy for it.

What does the licence line say?

Source: Meta's terms page, read 2026-10-09.

Licence and survival text (read 2026-10-09)
PointPage wording, shortened
GrantPerpetual, worldwide, non-exclusive, fully paid and royalty-free licence to use any Input for the purposes in the terms
Who grantsYou, by using the Ad Creative AIs
SurvivalSurvives termination of the terms by any party, for any reason
EffectiveCurrent date May 6, 2024; merge into Self-Serve Ad Terms on October 30, 2026

Which of your clips become Inputs?

The page ties the licence to use of the Ad Creative AIs through the Self-Serve Ad Interfaces or the Marketing API. A file you render in Sume and upload as the ad is not described as an Input on that page. A file you select inside a Meta generative feature is. If a clip carries a face, a product not yet launched, or a script under embargo, keep it out of those features.

How do you hand Meta a safe copy?

Cut a working copy that holds only what you accept being licensed. With video_trim you take a window from the master (start plus an end or a duration, 0.2 to 900 seconds, $0.02 per job). With Timeline 1.0 you can render a different edit entirely at $0.10 per output minute, rounded up. Both read workspace media URLs, so import the master first with a media import, and send an Idempotency-Key on writes.

Probe the copy with video_inspect before you hand it over; the probe is billed by its Modal compute. Keep the master and the copy under different names so the log shows which one went where.

What does this post not decide?

It does not interpret the licence for your company. Meta's page says the grant is to Meta for the purposes described in the terms; read those terms, or ask counsel, before putting customer footage into any feature. Sume's docs do not describe provenance marks, so nothing here claims Sume adds or removes them.

One more habit helps. Give the working copy a name that says it is for a Meta generative feature, and store its job ID with the ad request. If a clip later turns out to hold something you should not have shared, you will know in seconds which file went where and which creative IDs followed from it.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume