Auto-Add a Meme GIF to Every Lyric Line: How the Lyric GIF B-Roll Engine Works, and the Scripts

What it does

You already know the move: a lyric lands, a meme GIF punches it. Doing that by hand means searching a GIF for every line, downloading it, dropping it on the timeline, trimming it to the line. Forty lines is an evening. This does the whole thing from the timing sheet in about two minutes, and leaves you a project where every GIF is already cut to its line and two backups per line are one drag away.

The step that matters: lyric → meme query

Searching a GIF site for the lyric itself returns nothing useful. "Tiny words na ga hurt when I praise Jah" is not a GIF. What you actually type into a GIF search is the reaction the line calls for. That rewrite is the whole trick, and it is the part worth doing with care — by hand, or with an LLM, which is what I use. These are real rows from my song:

Lyric	Query the engine searched
Hou these myna birds brah	annoying birds squawking
Na ga mess with Mr Mayjah	don't mess with me
Tiny words na ga hurt when I praise Jah	unbothered
He na ga let ya	you shall not pass
You can not bug us	swatting fly
To flex the Mr Mayjah	flexing muscles
Mr Aloha, surely you know how	aloha hawaii shaka

Three rules that came out of the first run. Repeated hook lines get the same query but the engine rotates to a different GIF each time, so the chorus does not repeat itself. Every query carries two fallbacks, because some phrases return junk. And nothing that hits the timeline is final — the engine writes a review page with all three candidates playing side by side, you click the better one, and the project rebuilds from your picks without downloading anything again.

Which GIF search to build on (checked 5 September 2026)

This changed recently, and most guides online are now wrong. Apple's #images in Messages has no developer access at all — Apple's support page documents a search box and nothing else. Tenor, which powered a lot of GIF integrations, stopped accepting new API clients on 13 January 2026 and shut the API down on 30 June 2026. GIPHY still has an API: every key starts as a beta key limited to 100 calls an hour, production access is by application, and the terms require "Powered by GIPHY" attribution and forbid building your own GIF index from the results. KLIPY is the newer free alternative, also 100 calls an hour on a test key. Version 0.1 of the engine uses GIPHY; a 40-line song took 26 calls, so the free tier covers a couple of songs an hour.

The honest part about copyright

Meme GIFs are clips of other people's footage. Using them as b-roll in a monetised music video is the same grey zone as using #images in a Story — extremely common, rarely enforced, never actually cleared. I treat it like this: fine for edits and social cuts, and I keep the attribution the API returns (uploader and source page) in the project so I can find and swap anything if asked. If you want visuals you own outright, the same lyric-to-prompt step feeds an image or video generator instead of a GIF search. That is where I am taking this next.

Get the scripts

1. Unzip. Put your song's timing.txt from the Lyric Sync Timer in songs/<your-song>/lines.txt. Point song.json at your audio file and, if you have one, your lyric-video render.
2. Write queries.json — one meme phrase plus two fallbacks per line. The example for my song is included so you can see the shape. Paste the lyrics into an LLM with the table above as the pattern if you want it done in a minute.
3. Create a free GIPHY API key at developers.giphy.com. Double-click the RUN file; it asks for the key once and stores it locally.
4. It writes <Song>_GIF_BROLL.xml (Premiere: File → Import), <Song>_GIF_BROLL_fullbleed.mp4, and review.html. Swap picks in the review page, save picks.json into the song folder, run again.

python3 run.py songs/my-song              # search + download + Premiere XML + review page
python3 run.py songs/my-song --rebuild    # rebuild from picks.json, no network
python3 render_mp4.py songs/my-song       # MP4: GIF full-frame, lyrics keyed over it
python3 render_mp4.py songs/my-song panel # MP4: GIF in a framed box above the lyrics

Questions people ask

Can it use my iMessage #images GIFs?

No, and nothing can. #images is a closed Apple feature with no API. The same GIFs are on GIPHY and KLIPY, which do have APIs; that is what the engine searches.

Does it work with CapCut or After Effects?

Not yet. The XML is Final Cut Pro 7 format, which Premiere Pro and DaVinci Resolve import. After Effects would take a script built from the same picks file. CapCut has no official import path, and the open-source draft writers currently need Windows CapCut to export, so I have not built that.

Why an MP4 as well as a project file?

Because I had not installed Premiere yet on the machine I was working on. The MP4 render takes about 40 seconds and is good enough to post; the project file is for when you want to re-cut.

Does it need the lyric video to already exist?

No. Without a base video the MP4 is GIFs and your audio; with one, the lyric text is keyed over the GIFs. The timing sheet is the only thing it actually needs.

References

1. Apple Support — Send and save GIFs on your iPhone or iPad (#images) — retrieved 5 September 2026
2. Google Tenor Help — Tenor API service discontinuation — retrieved 5 September 2026
3. GIPHY Developers — API documentation (beta key rate limit) — retrieved 5 September 2026
4. GIPHY — API Terms of Service — retrieved 5 September 2026
5. KLIPY — Developers — retrieved 5 September 2026
6. pyCapCut — CapCut draft generator (Windows export note) — retrieved 5 September 2026