<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Cicadas.ai</title>
    <description>The latest articles on DEV Community by Cicadas.ai (@cicadasai).</description>
    <link>https://dev.to/cicadasai</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4197092%2F930cfb78-ceda-4e21-9ae2-dc5b57d1e6a3.png</url>
      <title>DEV Community: Cicadas.ai</title>
      <link>https://dev.to/cicadasai</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/cicadasai"/>
    <language>en</language>
    <item>
      <title>How to Make an Original Rap Instrumental Without Naming a Famous Producer</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Wed, 18 Nov 2026 01:39:12 +0000</pubDate>
      <link>https://dev.to/cicadasai/how-to-make-an-original-rap-instrumental-without-naming-a-famous-producer-54ml</link>
      <guid>https://dev.to/cicadasai/how-to-make-an-original-rap-instrumental-without-naming-a-famous-producer-54ml</guid>
      <description>&lt;p&gt;The fastest way to get the wrong rap beat is to start with someone else's name. Type-beat culture trains you to search that way: you hear a record you like, you name the person who made it, and you look for something close. Carry that habit into an AI prompt and you are no longer briefing a style. You are asking a model to lean on a real producer or a real artist, which sits in the same family of imitation that gets tracks pulled — a borrowed name in a title, a voice that is not yours, or a face that is not yours on a cover.&lt;/p&gt;

&lt;p&gt;You do not need that name to get a usable instrumental. You need a lane that matches how you actually rap, a mixed file with drums and bass already in place, and a way to choose between a couple of takes before you spend the evening fighting the music.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I build Punchline.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Brief the lane, not a person
&lt;/h2&gt;

&lt;p&gt;A useful brief for a rap instrumental is almost boring: boom bap or drill, melodic or cold, slower or faster than your natural pace. That is a style. A famous name is a shortcut around that decision, and it points the work at a person you do not have the right to imitate.&lt;/p&gt;

&lt;p&gt;Punchline's home page, as of a check on 18 November 2026, says making songs from your own lyrics and an original beat with AI is legal, and that what gets songs removed and accounts closed is imitation: an AI copy of a real artist's voice, their name in your title, or their face on your cover. The site says it does not offer those. That wording is the site's, not a lawyer's letter, and the same page says distributors apply their own rules, which change often. Describe the lane, and leave people out of the prompt.&lt;/p&gt;

&lt;p&gt;The AI beat maker page is built around that rule. It has no artist presets and no box for an artist's name. The FAQ says the tool takes a style from the menu and nothing else, so there is nowhere to type a name, and that Punchline tools make original material and do not imitate real artists, their songs or their producers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Let your delivery pick the style
&lt;/h2&gt;

&lt;p&gt;The page lists ten styles in one Beat style menu, in this order: Boom bap, Trap, Drill, Melodic rap, Old school, West Coast, Lo-fi rap, Jersey club, Grime and Cloud rap. You cannot set an exact BPM or key; the page says the style choice carries that. If a beat comes back too fast or too slow, the FAQ tells you to try a neighbouring style or generate again.&lt;/p&gt;

&lt;p&gt;The method the page recommends is to start from your natural pace. Rap your verse with no music and tap your foot. A slow, heavy tap, it says, points to Boom bap, Old school or Lo-fi rap. A quick tap points to Trap, Drill, Grime or Jersey club. West Coast sits between those groups, with a bounce that suits a laid-back delivery. The page also groups the styles by use:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Boom bap, Old school: storytelling and wordplay&lt;/li&gt;
&lt;li&gt;Trap, Drill: short bars, heavy low end&lt;/li&gt;
&lt;li&gt;Melodic rap, Cloud rap: sung hooks, open space&lt;/li&gt;
&lt;li&gt;West Coast: bounce and laid-back flows&lt;/li&gt;
&lt;li&gt;Grime, Jersey club: fast, high-energy delivery&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Picking a beat against the mood of the lyrics can work, the page says, but you should do it on purpose.&lt;/p&gt;

&lt;p&gt;Here is a teaching example of my own, not a result from the tool. I would use a short practice verse about missing the last night bus after a late shift. If I say those lines slowly and my foot falls heavy, I would choose Boom bap or Lo-fi rap. If I clipped every line short and my tap sped up, I would start with Trap or Drill. The brief should come from your delivery, not from a name you admire.&lt;/p&gt;

&lt;h2&gt;
  
  
  What one style pick actually produces
&lt;/h2&gt;

&lt;p&gt;Once you know the lane, you need a file you can rap over. That is what &lt;a href="https://punchline.fm/ai-beat-maker" rel="noopener noreferrer"&gt;Punchline's AI beat maker&lt;/a&gt; is for. You sign in, choose one of the ten styles, and press Generate beat. The page says there is no lyrics box because there is no vocal: the result is an instrumental, as an MP3 download, in about a minute. Each beat costs 4 credits, a signed-in account is required, and the page says your inputs stay on this page.&lt;/p&gt;

&lt;p&gt;One control decides the result, according to the page. An AI music model is asked for hard drums, a clear 808 or bass line, and a loop-friendly arrangement in the style you picked. Each press makes a new beat, so two runs of the same style will not sound the same. When the file is ready, it plays in the result panel and an MP3 button appears next to the player. While the model works, the button shows "Producing…"; the page says the tab can sit in the background.&lt;/p&gt;

&lt;p&gt;I am describing the live page, not a generation I ran for this article. The page itself shows an example labelled "Example: Trap instrumental made with this tool," and a seven-second screen recording it describes as a real result captured from the page. Credits come back if a job fails, so you only pay for audio you actually receive. As of 18 November 2026 the pricing page lists a one-time Starter pack at $9.90 for 100 credits that never expire, Artist at $9.90 a month for 120, and Pro at $24.90 a month for 360; monthly plans keep free tools free and can be cancelled any time. I have not tested checkout. There is no free redo listed for beats.&lt;/p&gt;

&lt;p&gt;Because every press makes a new instrumental, the page's advice is to generate two or three takes in one style and choose — 8 or 12 credits — then save the MP3 or generate again. Do not change style after a single disappointing take. Move to a neighbour only if the pace is consistently wrong for your verse.&lt;/p&gt;

&lt;h2&gt;
  
  
  Judge each take with your voice, not your eyes
&lt;/h2&gt;

&lt;p&gt;The page asks you to rap your verse over each take from the top without stopping, and to judge five things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pace: you finish each bar without rushing or dragging&lt;/li&gt;
&lt;li&gt;Space: the melody leaves room in the middle for a voice&lt;/li&gt;
&lt;li&gt;Low end: the 808 or bass does not swallow your words on phone speakers&lt;/li&gt;
&lt;li&gt;Shape: there is a clear place where a hook could lift&lt;/li&gt;
&lt;li&gt;Length: it runs long enough for the verses and hooks you have planned&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Those tests beat asking whether the beat "sounds expensive." A melody that fills the midrange will fight your vocal, and an 808 that buries consonants on a phone will disappear the bars you care about. When I test a beat for my own writing — my listening habit, not a file I generated here — I do the phone-speaker pass last. Headphones flatter low end.&lt;/p&gt;

&lt;h2&gt;
  
  
  Write and record to the sections the file actually has
&lt;/h2&gt;

&lt;p&gt;Once you have a take, find the count before you rewrite anything. The page's advice is to nod along and say one, two, three, four; the snare or clap usually lands on two and four, and four counts make one bar. Play the beat through and note the time at which each section changes. Many rap songs alternate 16-bar verses with 8-bar hooks, the page says, but you should write to the sections your beat actually has. If it opens with eight bars of drums, do not start the hook at bar one. If a lift arrives at 0:42, that is where the hook belongs.&lt;/p&gt;

&lt;p&gt;To record, the page says to play the beat in headphones so it does not leak into the microphone, keep the vocal on its own track in whatever recording app you use, and set the beat a little quieter than feels natural, because a voice that has to fight the music sounds strained. Neighbouring tools, named here without links: Punchline's Studio, which the home page describes as recording over a beat in the browser with headphones, with the take tuned, mixed and mastered on your device; and the AI rap generator, which the beat maker FAQ says produces a complete track with an AI vocal for 20 credits.&lt;/p&gt;

&lt;h2&gt;
  
  
  When a free drum loop is the better first step
&lt;/h2&gt;

&lt;p&gt;If you are still placing kicks, start with the site's free drum machine pages. The beat maker FAQ says the rap beat maker and the other drum machine pages are free: a 16-step sequencer with six drum sounds that plays in your browser, with no sign-up. The rap beat maker, on the same page's related-tools copy, starts a boom bap loop at 90 BPM and lets you tap squares on the grid to change the kick, snare, hats, clap and 808. The WAV button on those free pages saves only a four-bar drum loop with no melody, which the FAQ calls the main reason to use the AI version. Use the grid to program drums yourself; use the AI beat when you want one mixed file, drums and bass already in place, with nothing to sequence and no software to install — that contrast is how the page describes the paid tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you release the song
&lt;/h2&gt;

&lt;p&gt;An original style brief is not the whole release checklist. The beat maker page tells you, before you release a song built on a generated instrumental, to read the terms on the site and your distributor's rules on AI-made audio. As of 18 November 2026, those terms say that subject to the terms and to the AI providers' terms, you may use the results in your own projects; that AI output can resemble output made for others, can contain errors, and may not be protected by copyright in every country; and that the site does not guarantee a generated song is free of third-party rights.&lt;/p&gt;

&lt;p&gt;The home page adds that distributors' AI rules change often, and that most ask that you hold the rights to everything in the track and do not pass the voice off as a real artist. Recording the final vocal yourself, it says, removes most of the questions. Treat this as the site's wording, then check the current rules for your store or platform. Leave other people's names off the brief, the title, and the cover. The beat should sound like the lane you picked. The voice on the finished song should be yours.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I build Punchline.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>music</category>
      <category>tutorial</category>
      <category>rap</category>
    </item>
    <item>
      <title>The empty lead-in still loops with the joke — cut those frames and keep each delay</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 13:25:14 +0000</pubDate>
      <link>https://dev.to/cicadasai/the-empty-lead-in-still-loops-with-the-joke-cut-those-frames-and-keep-each-delay-27i3</link>
      <guid>https://dev.to/cicadasai/the-empty-lead-in-still-loops-with-the-joke-cut-those-frames-and-keep-each-delay-27i3</guid>
      <description>&lt;p&gt;You already have the animated GIF. The joke lands, the cursor finishes typing, the neon sign flickers — and then the file loops back through two seconds of nothing. Every replay makes the viewer wait through the same empty lead-in, or sit on a dead tail after the moment has already happened. Drawing a tighter crop box will not help: the picture may get smaller, but the wait is still in the file. Speeding the whole clip up is the wrong kind of fix as well, because it also hurries the part you wanted people to watch.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I build LoopGIF.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The capabilities, limits, and numeric examples below are taken from the live Cut GIF page as I fetched it on 17 November 2026 (Asia/Shanghai). They are the page’s published facts and examples, not a local test I ran for this piece.&lt;/p&gt;

&lt;h2&gt;Cutting is a time-range job, not a crop&lt;/h2&gt;

&lt;p&gt;Cutting a GIF means keeping a run of frames and dropping the rest. The animation gets shorter. The picture stays the same size. That is a time problem: you are choosing when the loop starts and when it stops.&lt;/p&gt;

&lt;p&gt;Cropping is a space problem. A crop keeps a rectangle of every frame, so the picture gets smaller and the length stays the same. If the trouble is an empty opening, a long wait after the punchline, or one glitch in the middle, a crop box cannot reach it. Those frames are still in the timeline, and the loop will still play them.&lt;/p&gt;

&lt;p&gt;If you later need both a shorter clip and a tighter picture, cut first and crop second, because the crop then works on fewer frames. This article is only about the time cut. The tool described here does not crop the picture, and it does not change how fast the kept frames play.&lt;/p&gt;

&lt;h2&gt;Keeping the rhythm is not the same as changing speed&lt;/h2&gt;

&lt;p&gt;A GIF does not have one global speed you can turn down in order to skip a boring start. Each frame already carries its own delay — the time it stays on screen. When you keep a frame, that delay stays with it. The part you keep plays at the same speed as before. The typing rhythm does not suddenly rush. The flicker does not slow down. What changes is which frames are still there.&lt;/p&gt;

&lt;p&gt;That also means a deletion is not a hold. If you remove a frame, you also remove its time on screen. The new GIF is shorter, and the animation jumps across the gap. If what you actually wanted was to keep the total length and leave the previous picture on screen for longer, that is a timing edit, not a cut. The cut tool does not rewrite delays. It keeps each kept frame’s own timing and drops the rest.&lt;/p&gt;

&lt;p&gt;This is why a long lead-in should be cut rather than “fixed” by speeding the whole file. A speed change would also hurry the joke, the typing, or the flicker you meant to preserve. A frame-range cut drops the wait and leaves the useful delays alone.&lt;/p&gt;

&lt;h2&gt;The unit of a cut is a frame&lt;/h2&gt;

&lt;p&gt;A GIF has no sub-frame time. You cannot cut in the middle of a frame. The unit of cutting is the frame itself: the first frame you want to keep, the last frame you want to keep, and, if you need it, individual frames inside that range.&lt;/p&gt;

&lt;p&gt;That sounds coarse until you remember how a GIF is built. The timeline is already a sequence of pictures, each with a delay. There is no hidden clock between two frames that a trimmer could split. If a gesture sits in one frame and the next frame is already the aftermath, your cut has to choose one side or the other. The summary line on a serious cutter should tell you both how many frames you are keeping and how many seconds the cut will last, so you can aim at “the three seconds that carry the joke” in frame units rather than guessing.&lt;/p&gt;

&lt;h2&gt;Two ways to drop time: a range, or a single bad frame&lt;/h2&gt;

&lt;p&gt;Most trims are a range. You set a first frame and a last frame. Everything outside that range is discarded. This is the right move when the file has a lead-in you do not want, or a dead tail after the action, or when only the first half of a long banner is useful.&lt;/p&gt;

&lt;p&gt;Sometimes the start and end are already right, and the problem is one frame in the middle: a glitch, a blink, a stray cursor or pointer. In that case you leave the range alone and delete the bad frame. The cut still starts and ends where it did, but the animation is shorter and it jumps over the gap. You can put the frame back if the jump looks worse than the glitch.&lt;/p&gt;

&lt;p&gt;Those two edits stack. You can keep a middle run of frames and still cross out a bad frame inside that window. Only frames inside the start and end range can be toggled. A restore control is there for the moment you delete too many and want every deletion undone at once.&lt;/p&gt;

&lt;h2&gt;How to cut the GIF in the browser&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://loopgif.net/cut-gif" rel="noopener noreferrer"&gt;LoopGIF’s cut GIF tool&lt;/a&gt; does this in the browser. It is free, requires no sign-up, and nothing is uploaded. There is no watermark, and you need no account. It accepts a GIF only, up to 25 MB and 300 frames. I did not run the tool locally for this piece; the steps and limits here are from the live page as fetched on 17 November 2026.&lt;/p&gt;

&lt;p&gt;Drop a GIF onto the box, or click to choose a file. Its frames appear as a strip of thumbnails. Move the Start and End sliders to the first and last frame you want to keep. Frames outside the range fade, and the part inside the range stays at full strength, so you can see the cut before you make it. The summary shows how many frames are kept and how long the cut lasts.&lt;/p&gt;

&lt;p&gt;If a frame inside that range should go, click it in the strip to cross it out and leave it out of the new GIF. Click it again to bring it back. Restore all frames undoes every deletion.&lt;/p&gt;

&lt;p&gt;Watch the preview, then press Cut GIF. The tool draws the kept frames with their own delays and writes a new GIF in your browser. The shorter GIF appears with its size and frame count, and Download saves it. The preview uses small thumbnails; the exported GIF is the real thing. The page says the tool was built and tested in current Chrome, and that it checks the browser you are using right now — by asking it directly, not by guessing from the name — for GIF files and for background encoding with Web Workers. The tool requires JavaScript.&lt;/p&gt;

&lt;h2&gt;What the published examples actually cut&lt;/h2&gt;

&lt;p&gt;The live page publishes four cuts, each made from one of LoopGIF’s own GIFs with the tool’s own cut code. These numbers are the page’s examples, not measurements I made.&lt;/p&gt;

&lt;p&gt;One is a pink neon Open sign flickering in 12 frames at 480 × 270. Keeping frames 3 to 10 trims the start and end of the flicker and leaves the part with the most going on. The file goes from 130 KB to 89 KB, still 480 × 270, now 8 frames.&lt;/p&gt;

&lt;p&gt;Another is a bouncing ball in 16 frames at 480 × 270. The whole range is kept, but frames 4, 5, 6 and 7 are deleted. The start and end do not change; the animation jumps over the gap, and the file goes from 34 KB to 25 KB, now 12 frames.&lt;/p&gt;

&lt;p&gt;A third is an orange LED sign scrolling in 57 frames at 480 × 120. Keeping the first 28 frames is a simple first-half trim. Each kept frame keeps its own delay, so the half that is left plays at the same speed as before. The file goes from 215 KB to 106 KB, still 480 × 120, now 28 frames.&lt;/p&gt;

&lt;p&gt;The fourth is a terminal typing animation at 480 × 270. Keeping frames 9 to 33 skips the empty start. Because every kept frame keeps its delay, the typing rhythm is unchanged. The file goes from 28 KB to 22 KB, now 25 frames.&lt;/p&gt;

&lt;p&gt;Taken together, the examples make the same argument as the page’s own list of when a cut helps. You cut off a lead-in so the GIF begins on the action. You keep the few seconds that carry the joke and drop the rest. You delete a single bad frame. And because fewer frames means fewer bytes, a cut is also a quick way to a lighter file. If you plan to join several clips later, trim each one first so you are not combining lead-ins and dead tails.&lt;/p&gt;

&lt;h2&gt;Limits that change the result&lt;/h2&gt;

&lt;p&gt;The cut is made on your device. The GIF is opened, cut and re-encoded in your browser. Nothing is sent to a server.&lt;/p&gt;

&lt;p&gt;The input limits are 25 MB and 300 frames. The cut itself is capped at 300 frames and 30 seconds of playing time. If you were hoping to slice a long, heavy file down to a short loop, those caps are the ceiling, not a target.&lt;/p&gt;

&lt;p&gt;Because the output is a fresh encode, the file may be slightly different in size from a simple trim, and colour is reduced to a shared palette. Transparency is kept. The output is limited to 1024 px on the longer side, so a very wide or tall source can come out smaller in pixels even though a cut is not a crop. The cut GIF always loops forever. That last point matters if the original was meant to play once and stop: after the cut, it will not stop.&lt;/p&gt;

&lt;p&gt;None of those limits turn a time cut into a spatial crop, a reversal, or a speed change. They only describe what happens to the frames you decided to keep.&lt;/p&gt;

&lt;p&gt;If the empty start is still in the loop, the fix is to drop those frames and leave every kept delay alone.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I build LoopGIF.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>tutorial</category>
      <category>design</category>
      <category>webdev</category>
    </item>
    <item>
      <title>A locked 9:16 crop can cut the side text — place the box, then play the whole loop</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 12:50:47 +0000</pubDate>
      <link>https://dev.to/cicadasai/a-locked-916-crop-can-cut-the-side-text-place-the-box-then-play-the-whole-loop-4aig</link>
      <guid>https://dev.to/cicadasai/a-locked-916-crop-can-cut-the-side-text-place-the-box-then-play-the-whole-loop-4aig</guid>
      <description>&lt;p&gt;&lt;em&gt;I build LoopGIF.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You already have an animated GIF that works. It may have empty margins, the wrong shape for a square or tall slot, or clutter in a corner you do not want. The tempting shortcut is to squeeze the whole picture into the new shape. That changes the proportions of every face and every letter. Cropping is a different job: you draw a box, everything outside it is discarded, and the pixels inside stay the same size.&lt;/p&gt;

&lt;p&gt;Two things still go wrong. A locked shape such as 9:16 keeps a centred strip and can cut the caption on the sides. And the box you place on the first frame is the same box on every other frame. If a subject moves, it can walk out of the cut. Place the box on the part that must survive, then play the preview all the way through before you commit.&lt;/p&gt;

&lt;h2 id="cropping-cuts-pixels-away-it-does-not-stretch-them"&gt;Cropping cuts pixels away. It does not stretch them.&lt;/h2&gt;

&lt;p&gt;Cropping removes part of the picture. The pixels outside the box are gone. The pixels inside are not scaled, squashed, or stretched. Faces stay the same shape. Lettering keeps its proportions. The GIF gets smaller in pixels because it covers less of the original, not because anything was redrawn at a new size. The output, by default, is the pixel size of the box itself: a cut, not a scaled copy.&lt;/p&gt;

&lt;p&gt;Use a crop to drop a border, cut empty space around a subject, or change the shape of the frame without distorting what remains. Resizing is the other job: it keeps the whole picture and changes how many pixels it is drawn with. If you still need exact dimensions after choosing the region, that is a later step. If cutting would throw away too much of a scene you need in full, squeezing the whole frame is a different decision, and it will distort faces and type. Do not treat the two as interchangeable.&lt;/p&gt;

&lt;h2 id="one-box-applies-to-every-frame"&gt;One box applies to every frame&lt;/h2&gt;

&lt;p&gt;One crop box applies to every frame. You cannot change the box over time, and the tool does not add, remove, or reorder frames. Each frame keeps its own delay, so the timing of the loop is unchanged. What changes is only which pixels remain.&lt;/p&gt;

&lt;p&gt;That is easy to miss if you place the box on a single still. A subject in the middle of frame one may drift toward an edge later in the loop. If that edge is outside the box, the subject walks out of the cropped file. Play the preview with the box in place and watch the whole loop, not only the first frame. If the moving part leaves the box, enlarge it or move it toward the subject’s path, and play it again.&lt;/p&gt;

&lt;p&gt;A published example makes that concrete. A free-shape crop of the left half of a 480 × 120 scrolling banner uses a 240 × 120 box at x 0, y 0. The file goes from 215 KB to 117 KB. All 57 frames are kept, so the scroll still plays — in the remaining half of the picture.&lt;/p&gt;

&lt;h2 id="a-locked-shape-can-cut-the-text-you-meant-to-keep"&gt;A locked shape can cut the text you meant to keep&lt;/h2&gt;

&lt;p&gt;You pick a locked shape so the output will be a square, a tall 9:16, a 4:5 portrait, a 16:9 widescreen, or a 4:3 frame. The box becomes the largest one of that shape that fits inside your current box, centred on it. That is convenient, and it is not the same as protecting the part of the picture you care about.&lt;/p&gt;

&lt;p&gt;The page’s published 9:16 example is the caution. On a 320 × 320 square GIF, the tallest 9:16 box that fits is 180 × 320 at x 70, y 0. It uses the full height and keeps the middle strip. The file goes from 320 KB to 214 KB, still 16 frames, now 180 × 320. It also cuts away part of the meme text on the sides. The shape is exact, to the nearest pixel. The words on the edges are not.&lt;/p&gt;

&lt;p&gt;The page’s other published examples show the same pattern:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;1:1 on a 480 × 270 GIF: a 270 × 270 box at x 105, y 0. The centred sign stays in frame, 130 KB to 124 KB, 12 frames. That worked because the sign was already in the middle; type on the left would have been cut.&lt;/li&gt;
&lt;li&gt;4:5 on a 320 × 320 sticker: a 256 × 320 box at x 32, y 0, keeping the bear and trimming a strip from each side, 221 KB to 215 KB, 16 frames.&lt;/li&gt;
&lt;li&gt;4:3 pulled to the top left of a 480 × 270 GIF with the X and Y fields: a 360 × 270 box at x 0, y 0, keeping the left edge of the text and dropping the empty right side, 28 KB to 26 KB, 33 frames.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Pick the shape if you need that proportion, then move the box onto the part that must survive, and only then crop. Locking a ratio keeps a centred region of that shape. It will not, by itself, keep the caption, the face, or the product in frame.&lt;/p&gt;

&lt;p&gt;Apps change their size rules, so check the current guidelines of the place you post to rather than relying on a remembered pixel size. For the shape itself, the crop is exact to the nearest pixel. Aspect shapes are rounded to whole pixels, so 16:9 on an odd width can be a pixel off. That is a rounding limit, not a reason to stretch the picture.&lt;/p&gt;

&lt;h2 id="how-to-place-the-box-and-cut-the-gif"&gt;How to place the box and cut the GIF&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://loopgif.net/gif-cropper" rel="noopener noreferrer"&gt;LoopGIF’s GIF cropper&lt;/a&gt; does this in the browser. It is free, requires no sign-up, and nothing is uploaded. There is no watermark. It accepts a GIF only, up to 25 MB and 300 frames. I did not run the tool locally; the capabilities, limits, and numeric examples here are from the live page as fetched on 17 November 2026, including the page’s own published examples.&lt;/p&gt;

&lt;p&gt;Drop a GIF onto the box, or click to choose a file. The animation appears with a crop box over it. Drag the box to move it. Drag any corner to resize it: the opposite corner stays where it is. On a phone or tablet, you drag with your finger. Arrow keys nudge the focused box by one pixel, or ten with Shift. The X and Y fields set the top-left corner in pixels; Width and Height set its size. Reset brings back the whole picture.&lt;/p&gt;

&lt;p&gt;The box is whole pixels and stays inside the picture. It cannot be smaller than 1 pixel, and the box handles stop at 8 pixels. Whatever sits outside the dimmed edge will be removed. Tap Free, 1:1, 4:3, 16:9, 9:16, or 4:5 to lock or unlock the shape. If you already know the exact cut, type the numbers. An optional max width of 480 or 320 scales the box down if you want a smaller output. By default the output is the pixel size of the box, and at most 1,024 pixels on the longer side.&lt;/p&gt;

&lt;p&gt;Press Crop GIF. Every frame is cropped to the same box, and the new file appears next to the original with its dimensions and file size, ready to download. It is a fresh encode, not a byte copy of a sliced original, with one shared palette of up to 255 colours plus transparency, so the size can be smaller or larger than the source. The published examples above all came out lighter, which is not a promise of a particular kilobyte budget. A specific file size after the crop is a separate compression step.&lt;/p&gt;

&lt;p&gt;Transparent GIFs stay transparent. Each frame keeps its own delay, and the frame count is unchanged. Very large dimensions are refused if they would not fit in memory. The GIF is opened, cropped, and encoded in your browser. It works in current Chrome, Edge, Firefox, and Safari, with touch dragging on phones and tablets. Browsers that cannot decode GIFs natively use a built-in decoder, and the tool tells you which one it used.&lt;/p&gt;

&lt;p&gt;Only crop GIFs you have the right to change. There is an optional AI path on the same page if you want a new GIF rather than a different crop of the one you have. That path needs a signed-in account and costs 1 credit per AI GIF. The free cropper stays free. I am not describing a purchase flow.&lt;/p&gt;

&lt;h2 id="a-short-checklist-before-you-crop"&gt;A short checklist before you crop&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;If the whole picture has to remain and only the pixel size should change, that is resizing, not cropping.&lt;/li&gt;
&lt;li&gt;Place the box on the part that must survive. A locked shape will not protect side or top text by itself.&lt;/li&gt;
&lt;li&gt;Play the whole loop. The box does not move from frame to frame. If a subject leaves the box, enlarge it or shift it and watch again.&lt;/li&gt;
&lt;li&gt;Use the X, Y, Width, and Height fields, or the arrow keys, for an exact-pixel cut. Use a max width of 480 or 320 only if you also want the cut scaled down.&lt;/li&gt;
&lt;li&gt;After you download, confirm the region, the timing, and that nothing important was cut.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You do not need a new GIF. You need the one you already have, cut to the region that matters, with the pixels inside still the same size, and with the subject still inside the box for the whole loop.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I build LoopGIF.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>tutorial</category>
      <category>design</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Your square GIF looks tall because you chose Stretch — crop to a centred square first</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 12:23:46 +0000</pubDate>
      <link>https://dev.to/cicadasai/your-square-gif-looks-tall-because-you-chose-stretch-crop-to-a-centred-square-first-3jn0</link>
      <guid>https://dev.to/cicadasai/your-square-gif-looks-tall-because-you-chose-stretch-crop-to-a-centred-square-first-3jn0</guid>
      <description>&lt;p&gt;&lt;em&gt;I build LoopGIF.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You already have the animated GIF. It looks fine at its original width and height. Now it has to fit a new box: a square reaction slot, a narrow blog column, a template that asks for exact pixel dimensions. The tempting move is to type the new width and height, turn the aspect lock off, and Stretch the picture into the new shape. The file still loops. The mark does not look like itself: a wide wordmark becomes tall and thin. You changed the shape of every frame.&lt;/p&gt;

&lt;p&gt;Fitting an already-made GIF to a new size is a geometry problem first and a file-size problem second. The two mistakes that do the most damage are stretching a picture into a different aspect ratio, and scaling a small original up as if extra pixels could invent detail that was never there.&lt;/p&gt;

&lt;h2 id="stretch-changes-the-shape-crop-to-fill-keeps-it"&gt;Stretch changes the shape. Crop to fill keeps it.&lt;/h2&gt;

&lt;p&gt;When the aspect lock is on, you set one side and the other follows, rounded to whole pixels. The picture stays the same shape — the safe default when you are only changing scale.&lt;/p&gt;

&lt;p&gt;When you need a different shape — usually a square from a wide or tall source — turn the lock off and set both sides yourself. Then you have two choices, and they are not interchangeable.&lt;/p&gt;

&lt;p&gt;Stretch redraws the whole picture into the new box. Every frame is squeezed or pulled until it fits. If the source is wider than it is tall and the target is a square, the letters get taller relative to their width. That is what Stretch does, and it is the right choice only when distortion is what you want.&lt;/p&gt;

&lt;p&gt;Crop to fill does the other job. It cuts the picture to the new aspect first, keeping a centred region, then scales that region to the target size. Letterforms stay in proportion. What you lose is whatever sat outside that centred cut — the left and right of a wide frame, or the top and bottom of a tall one.&lt;/p&gt;

&lt;p&gt;The tool’s own published examples make the difference visible on the same wide source. A 480 × 270 GIF, run through the 128 × 128 emoji preset with Crop to fill, is cut to the middle 270 × 270 square and then scaled to 128 × 128. The file goes from 34 KB to 15 KB. The letters stay undistorted. The same source, with the lock off and Stretch on, squeezed into 256 × 256, goes from 34 KB to 32 KB — almost no change in bytes — and the letters look tall. The output size in pixels is not what wrecked the mark. The fill mode is.&lt;/p&gt;

&lt;p&gt;The 128 × 128 and 256 × 256 emoji presets are built around that lesson. Both switch the aspect lock off and choose Crop to fill, so a wide or tall GIF is cut to a centred square and then scaled, rather than squeezed. After you download, open the result and check that the part you care about is still in the middle. If the mark sits off to one side in the original, a centred crop can clip it, and you will need to choose the square yourself before you scale.&lt;/p&gt;

&lt;p&gt;Those two presets are usual starting points for a small square, not a promise that every app will accept the file. Apps set their own rules for dimensions, file size, and whether animation is allowed, and those rules change. Check the current guidelines of the app you upload to before you commit to a size. I am not going to quote a platform limit here, because any number I write will go stale.&lt;/p&gt;

&lt;h2 id="downscaling-shrinks-pixels-and-bytes-upscaling-does-not-add-detail"&gt;Downscaling shrinks pixels and bytes. Upscaling does not add detail.&lt;/h2&gt;

&lt;p&gt;With the aspect lock on, making a GIF smaller is the reliable path. Half the width and half the height is a quarter of the pixels, so the file usually drops by more than half, and edges often look sharper at the new size because the picture has been reduced, not invented.&lt;/p&gt;

&lt;p&gt;The page’s published examples:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Scale by 50% with the lock on: 320 × 320 down to 160 × 160, 320 KB to 129 KB, 60% smaller, still 16 frames.&lt;/li&gt;
&lt;li&gt;Scale by 25% with the lock on: 480 × 270 down to 120 × 68, 130 KB to 17 KB, 87% smaller, 12 frames — a thumbnail-sized loop from a 480 px source.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If a GIF is simply too wide for a page, the 480 px wide and 640 px wide presets do the same kind of work. They bring a large loop down so it fits a blog column or an email, without changing its shape.&lt;/p&gt;

&lt;p&gt;Upscaling goes the other way. The tool will do it, up to 1,024 pixels on the longer side, but it can only stretch the pixels it already has. The picture gets larger and a little soft, and the file grows. Nothing that was not in the original appears. Pixel art and hard-edged lettering suffer most.&lt;/p&gt;

&lt;p&gt;One published example: a 360 × 240 GIF scaled up, aspect locked, to 480 × 320 with the 480 px wide preset. The file goes from 44 KB to 90 KB, 103% larger, and no new detail appears. If you need a bigger GIF, start from the largest original you have. You cannot recover sharpness that a small export already discarded.&lt;/p&gt;

&lt;p&gt;Typing a number above 1,024 is not a way around the cap. The longer side is brought back to 1,024, and with the lock on, the other side follows. The output also cannot go below 8 pixels on a side.&lt;/p&gt;

&lt;h2 id="the-animation-speed-does-not-change-the-palette-might"&gt;The animation speed does not change. The palette might.&lt;/h2&gt;

&lt;p&gt;Resizing a GIF means redrawing every frame at the new size and writing those frames out as a new GIF. Each frame keeps its own delay, so the animation plays at the same speed with the same number of frames. You are not re-timing the loop. You are changing how large each picture is.&lt;/p&gt;

&lt;p&gt;The result is a fresh encode, not a byte copy of the original. Colours are re-quantised to one shared palette of up to 255 colours plus transparency, with no dithering. Transparent GIFs stay transparent. Because it is a new encode, the file can come out smaller or larger than the source.&lt;/p&gt;

&lt;p&gt;That is why the Smaller file tick is easy to misunderstand. It uses 127 colours and ignores tiny colour changes between frames. It is a palette and similarity trade, and it can make a lighter file. It is not a substitute for picking the right dimensions. If the GIF is too wide for the slot, shrink the pixels. If you stretched a wide source into a square, reducing the colour count will not unsquash the letters. If you need a particular size in kilobytes rather than a particular size in pixels, that is a compression problem, and a smaller palette will not always get you to a specific budget.&lt;/p&gt;

&lt;h2 id="how-to-set-the-size-without-wrecking-the-mark"&gt;How to set the size without wrecking the mark&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://loopgif.net/gif-resizer" rel="noopener noreferrer"&gt;LoopGIF’s GIF resizer&lt;/a&gt; does this in the browser. It is free, requires no sign-up, and nothing is uploaded. There is no watermark. It accepts a GIF only, up to 25 MB and 300 frames, and it shows the current width, height, frame count and file size when you drop a file in.&lt;/p&gt;

&lt;p&gt;From there the controls are straightforward:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Type a width or a height, with the aspect lock on if you want the other side to follow.&lt;/li&gt;
&lt;li&gt;Or tap a scale chip: 25%, 50%, 75%, 150%, or 200%.&lt;/li&gt;
&lt;li&gt;Or use a preset: 128 × 128 emoji, 256 × 256 emoji, 480 px wide, or 640 px wide.&lt;/li&gt;
&lt;li&gt;If you turn the lock off, choose Stretch or Crop to fill before you run it.&lt;/li&gt;
&lt;li&gt;Tick Smaller file only if you want the 127-colour, ignore-tiny-changes encode.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Press Resize GIF. The new file appears next to the original, with its dimensions and the file size before and after, ready to download.&lt;/p&gt;

&lt;p&gt;A practical order of decisions:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Start from the largest original you have. Do not upscale a small export if a larger source still exists.&lt;/li&gt;
&lt;li&gt;If you only need a smaller version of the same shape, leave the aspect lock on and type a side, or use 25%, 50%, 75%, or a 480 / 640 px wide preset.&lt;/li&gt;
&lt;li&gt;If a template asks for an exact width and height that does not match the original aspect, turn the lock off and use Crop to fill so nothing is stretched. Then check that the part you care about is still in the middle.&lt;/li&gt;
&lt;li&gt;Use Stretch only when you actually want the picture to change shape.&lt;/li&gt;
&lt;li&gt;Treat Smaller file as a palette trade after the dimensions are right, not as the way to choose the size.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The work stays on your device: the GIF is opened, resized and encoded in the browser. Files with very large dimensions can be refused if they would not fit in memory. Current Chrome, Edge, Firefox and Safari are supported. Browsers that cannot decode GIFs natively use a built-in decoder, and the tool tells you which one it used.&lt;/p&gt;

&lt;p&gt;You do not need a new GIF. You need the one you already have, at the size the layout actually uses, with the mark still the same shape it was when you made it.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I build LoopGIF.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>tutorial</category>
      <category>design</category>
      <category>webdev</category>
    </item>
    <item>
      <title>If a looping GIF has to spell a name correctly, set the type — don't prompt it</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 11:54:25 +0000</pubDate>
      <link>https://dev.to/cicadasai/if-a-looping-gif-has-to-spell-a-name-correctly-set-the-type-dont-prompt-it-hd1</link>
      <guid>https://dev.to/cicadasai/if-a-looping-gif-has-to-spell-a-name-correctly-set-the-type-dont-prompt-it-hd1</guid>
      <description>&lt;p&gt;A name in a looping GIF looks simple until the letters are wrong. You want the file to say Maya, or OPEN, or thank you — spelled exactly as you typed it, in every frame. Two shortcuts keep failing that test.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I build LoopGIF.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The first shortcut is a screenshot of type. You get the spelling for free, because a font rendered it, and then you have a still. Scaling that bitmap, fading it, or sliding it around is awkward: the letters are no longer type, they are a picture of type, already rasterized at one size and one weight. If you need a different colour or a tighter crop, you go back to the design tool and shoot another frame.&lt;/p&gt;

&lt;p&gt;The second is asking an image model to “draw the word OPEN in neon.” The model is not setting type. It is synthesizing letter-shaped pixels from a description. An O can grow a serif it should not have, an E can become an F two frames later, and a four-letter word can arrive as five. In a short loop you see that misspelling every couple of seconds, which is worse than a static typo, because the animation keeps calling attention to it.&lt;/p&gt;

&lt;p&gt;The reliable way is to keep the string as text and draw it with a font on every frame. The motion can bounce, wave, or flicker. The spelling cannot drift, because nothing is guessing the letters.&lt;/p&gt;

&lt;h2 id="typography-is-a-string-a-picture-of-typography-is-not"&gt;Typography is a string. A picture of typography is not.&lt;/h2&gt;

&lt;p&gt;When a layout program or a browser draws “Nina”, it maps four characters to glyphs in a font, then paints those outlines. Change the colour, the size, or the frame number, and the same four glyphs appear again. That is why a title card stays spelled correctly when you animate it in a motion tool or in CSS: the source is still a string.&lt;/p&gt;

&lt;p&gt;A screenshot throws that string away. An image model never had the string as type in the first place. It may have been trained on pictures of signs and book covers, and it can often produce something that &lt;em&gt;looks like&lt;/em&gt; lettering. “Looks like” is not the same as “reads as the name you need.” If the GIF is a greeting, a shop sign, or a two-word chat reaction, readable spelling is the whole point.&lt;/p&gt;

&lt;p&gt;So the job is: keep the characters, pick a typeface, then animate the already-correct lettering.&lt;/p&gt;

&lt;h2 id="set-the-type-then-pick-a-motion"&gt;Set the type, then pick a motion&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://loopgif.net/text-to-gif" rel="noopener noreferrer"&gt;LoopGIF's text-to-GIF tool&lt;/a&gt; has a free tab that does this in the browser. You type up to 200 characters, including line breaks and emoji, choose one of six effects, and download a GIF. Nothing is uploaded, no account is required, and the file has no watermark. Encoding starts when you click Download.&lt;/p&gt;

&lt;p&gt;The six effects are Typing, Slide, Glitter, Bounce, Neon glow, and Wave. Each one swaps in the controls it needs, but your text, canvas size, and transparency setting are kept when you switch. Thirteen bundled fonts, all under the SIL Open Font License, load on demand. You set size, alignment (left, centre, or right), and colours, or you tick Transparent background.&lt;/p&gt;

&lt;p&gt;For a name or a two- or three-word line, Bounce, Wave, Neon glow, and Glitter are the better fit: the whole word stays on screen, the viewer reads it once, and the effect is what repeats. Slide is the ticker: one line moving across the frame, with the loop length rounded to a whole number of steps so the wrap has no jump. Typing reveals letters over time, which is a different job — useful when the arrival of the words is the point, not when a finished name has to sit in a loop and be read at a glance.&lt;/p&gt;

&lt;p&gt;Before you export, the preview plays with the real frame timing and shows the frame count, the length, and an estimated file size. The page says that estimate is usually within about a quarter of the real file; check the downloaded GIF if the destination has a tight budget.&lt;/p&gt;

&lt;p&gt;A few constraints are worth planning around, because they come from the format and from the editor, not from taste:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The canvas can be up to 728 pixels wide, 640 pixels tall, and 307,200 pixels in area, and every GIF is capped at 150 frames.&lt;/li&gt;
&lt;li&gt;Frame delays are whole hundredths of a second and never below 2. The page notes that browsers play anything faster than that at 10 frames per second, so the editor does not offer a delay the player will ignore.&lt;/li&gt;
&lt;li&gt;GIF transparency is on or off, not semi-transparent. Soft edges on the letters are blended toward a matte colour you choose, so pick the colour of the page or chat background the file will sit on.&lt;/li&gt;
&lt;li&gt;Emoji are drawn with your device's emoji font, so they can look different on another system.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of those limits changes the spelling. The letters are still coming from a font.&lt;/p&gt;

&lt;h2 id="when-you-want-illustrated-lettering-anyway"&gt;When you want illustrated lettering anyway&lt;/h2&gt;

&lt;p&gt;Sometimes you do want the letters to look drawn — neon flicker, balloon forms, glitter that is a texture the font does not have. The same page has an AI tab for that, and it is honest about the difference.&lt;/p&gt;

&lt;p&gt;Describe a GIF turns a prompt into a short animated scene. It is the right mode when there are no words to protect, and a poor choice when a name has to be readable, because you are back to hoping the model letters the sign correctly.&lt;/p&gt;

&lt;p&gt;Animate words is the other mode: you supply the exact text, up to 40 characters, plus a style, and the page says that text is passed as an instruction that it must read exactly in every frame. Allowed characters are letters, digits, spaces, and a short list of marks such as ! ? . , ' &amp;amp; - : along with hearts or stars. The model draws at most 16 frames at about 512 pixels, so the motion is chunkier than the free effects, which can render many more frames from a formula.&lt;/p&gt;

&lt;p&gt;That tab needs a signed-in account and costs 1 credit per GIF. The free typography tab stays free. The page says a failed job is refunded, that generations usually arrive in under a minute, and that exporting an already-generated AI GIF at another width or speed in the browser is free. The prompt must not ask for real people or brand names. I am not describing a purchase flow; use this mode only if you already have an account and a credit, and always read the result frame by frame. An instruction to keep the spelling is not the same guarantee as a font.&lt;/p&gt;

&lt;p&gt;If you need exact colours, a specific bundled typeface, a custom canvas, or a longer line, stay on the free tab. If you need a decorated lettering style and the line is short enough, Animate words is the constrained path. Do not put the name only in the style prompt and hope.&lt;/p&gt;

&lt;h2 id="a-short-checklist-for-a-name-or-a-line"&gt;A short checklist for a name or a line&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Type the words. Do not photograph them, and do not bury them in a scene prompt.&lt;/li&gt;
&lt;li&gt;Keep the line short enough to read at the size you will actually show. A name or two words can carry Bounce, Wave, Neon, or Glitter. A longer sentence belongs in Slide, or in ordinary text next to a simpler animation.&lt;/li&gt;
&lt;li&gt;Use a high-contrast colour pair. Motion does not help if the letters disappear into the background.&lt;/li&gt;
&lt;li&gt;Watch the loop in the preview, not only a single frame. Confirm that nothing in the effect (a hop, a wave, a flicker) makes a letter unreadable at the moment it should be read.&lt;/li&gt;
&lt;li&gt;If you go through Animate words, check every frame for a mutated glyph before you post the file.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A looping GIF that has to say a particular name is a typography problem first and an animation problem second. Set the type, then loop it.&lt;/p&gt;

&lt;p&gt;I build LoopGIF.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>gif</category>
      <category>tutorial</category>
      <category>design</category>
    </item>
    <item>
      <title>Your demo GIF finishes before reviewers can read it — change the delays, don't re-record</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 11:28:18 +0000</pubDate>
      <link>https://dev.to/cicadasai/your-demo-gif-finishes-before-reviewers-can-read-it-change-the-delays-dont-re-record-5107</link>
      <guid>https://dev.to/cicadasai/your-demo-gif-finishes-before-reviewers-can-read-it-change-the-delays-dont-re-record-5107</guid>
      <description>&lt;p&gt;A reviewer opens your pull request, watches the GIF loop twice, and still has not read the toast. The warning was in the recording and in the export. It was on screen, but not for long enough. Re-recording the same click path more slowly is a miserable fix when the frames you need are already in the file.&lt;/p&gt;

&lt;p&gt;I build LoopGIF. The timing rules below come from the GIF89a specification and from a 21-frame test file I encoded myself on 17 November 2026 (Asia/Shanghai) with Pillow 13.0.0, then checked by reading the Delay Time field in each Graphic Control Extension.&lt;/p&gt;

&lt;h2 id="a-gif-does-not-have-a-frame-rate.-it-has-per-frame-delays."&gt;A GIF does not have a frame rate. It has per-frame delays.&lt;/h2&gt;

&lt;p&gt;I fetched the &lt;a href="https://www.w3.org/Graphics/GIF/spec-gif89a.txt" rel="noopener noreferrer"&gt;GIF89a specification&lt;/a&gt; from the W3C. In the Graphic Control Extension, Delay Time is a 16-bit value. The spec says:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;If not 0, this field specifies the number of hundredths (1/100) of a second to wait before continuing with the processing of the Data Stream. The clock starts ticking immediately after the graphic is rendered.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;There is no global fps field. Each frame carries its own delay, in whole hundredths of a second. A tooltip can linger while the cursor stays snappy, but only if the encoder wrote it that way; many screen-recording exports instead stamp the same delay on every frame. Hundredths are a coarse grid: 40 ms is delay 4, 60 ms is delay 6, and 66.7 ms â€” one frame at 15 fps â€” is not a value the format can store.&lt;/p&gt;

&lt;h2 id="export-at-15-fps-is-not-a-playback-speed-control"&gt;â€œExport at 15 fpsâ€ is not a playback-speed control&lt;/h2&gt;

&lt;p&gt;Fifteen frames per second means 1000/15 â‰ˆ 66.7 ms per frame. I asked Pillow to write that number several ways, then read the file. For a 15-frame clip, a duration of 66 ms, 67 ms, or the floating-point value 1000/15 all produced a Delay Time of 6 hundredths (60 ms) on every frame. The loop lasted 0.900 seconds, which is 16.667 fps, not 15. Passing 70 ms produced delay 7 (70 ms). Those 15 frames lasted 1.050 seconds, or 14.286 fps. In this encoder, the conversion is integer division by ten: 66 and 67 both become 6. Another encoder might round 67 up to 7. Either way, you cannot hit 15 fps exactly, because 100/15 is not an integer.&lt;/p&gt;

&lt;p&gt;Re-exporting a recording at a lower frame rate usually means a video filter picking frames off a timeline. Some pictures disappear, and the one frame where a validation message is fully visible is easy to lose. Changing playback speed is different: leave the bitmaps alone, rewrite only the Delay Time values, and every picture stays. A uniform fps stamp also flattens uneven timing.&lt;/p&gt;

&lt;h2 id="a-file-i-actually-encoded"&gt;A file I actually encoded&lt;/h2&gt;

&lt;p&gt;I built a 21-frame, 360Ã—148 GIF of a fake â€œAPI tokensâ€ panel: typing a token, clicking Rotate, a three-frame toast (â€œSaved. Your API token was rotated.â€), and the aftermath. I wrote delay 4 (40 ms) on the 18 motion frames and delay 6 (60 ms) on the toast frames, and confirmed those values in the file. The header is &lt;code&gt;GIF89a&lt;/code&gt;. The first Graphic Control Extension is &lt;code&gt;21 f9 04 08 04 00 00 00&lt;/code&gt;, a Delay Time of 4 as the spec defines it. The loop is 90 hundredths, or 0.90 seconds. The toast is readable for 18 hundredths, or 0.18 seconds.&lt;/p&gt;

&lt;p&gt;I saved the same 21 bitmaps with new delays. The file stayed 58,840 bytes each time. A Ã—0.5 multiplier (delays doubled) wrote 8 and 12 hundredths: the loop lasted 1.80 seconds, and the toast hold stayed one and a half times longer than the motion frames. Ã—2 wrote 2 and 3 hundredths and lasted 0.45 seconds, still above the usual browser floor.&lt;/p&gt;

&lt;p&gt;Ã—4 is the trap. It wrote 1 hundredth on the 18 motion frames and 2 on the toast frames. The file claims 0.24 seconds. If a browser treats a delay of 0 or 1 as about 10 hundredths, those 18 frames play for 1.00 second instead of 0.18, and the loop plays for about 1.86 seconds â€” slower than the original, not four times faster. A fixed delay of 7 hundredths â€” the whole-hundredths value just above 66.7 ms â€” lasted 1.47 seconds and flattened the hold: the toast no longer lingers relative to the typing. Slowing the clip with a multiplier kept the pause on the message. Stamping a single â€œ15 fps-ishâ€ delay did not.&lt;/p&gt;

&lt;h2 id="the-floor-you-hit-when-you-try-to-go-faster"&gt;The floor you hit when you try to go faster&lt;/h2&gt;

&lt;p&gt;GIF89a does not define a minimum useful delay. It only says the field is used â€œif not 0.â€&lt;/p&gt;

&lt;p&gt;Eric Lawrence, in the archived IEInternals post &lt;a href="https://learn.microsoft.com/en-us/archive/blogs/ieinternals/trivia-animated-gif-timing" rel="noopener noreferrer"&gt;Trivia: Animated GIF Timing&lt;/a&gt; on Microsoft Learn, explained the legacy behaviour. Early tools wrote extremely low durations, such as 0 ms, and Internet Explorer delayed any frame of 50 ms or fewer (20 fps) to 100 ms (10 fps). An update in the same post says IE10 Consumer Preview allows a delay as little as 20 ms; anything lower is still delayed to 100 ms for legacy compatibility.&lt;/p&gt;

&lt;p&gt;I did not time a browserâ€™s clock myself. I did write the short values into files with Pillow: 0, 1, 2, or 5 ms stored as Delay Time 0; 10 through 19 ms as 1; and 20 ms as 2. Those â€œfaster than 20 msâ€ settings are the ones IE10 and its successors said they would not honor at face value. Designing for a floor of two hundredths (20 ms), and treating 0 or 1 in a source file as about ten, is the conservative rule. A GIF already at delay 2 often will not speed up: there is no shorter value you can write that a browser will play as shorter.&lt;/p&gt;

&lt;h2 id="how-to-retime-a-gif-you-already-have"&gt;How to retime a GIF you already have&lt;/h2&gt;

&lt;p&gt;Start from the existing file. Do not re-record unless a frame is actually missing. If the relative timing is right and the clip is simply too fast or too slow, scale every delay by the same factor so a hold stays a hold. If you want a steady pace, write one fixed delay on every frame instead.&lt;/p&gt;

&lt;p&gt;I maintain &lt;a href="https://loopgif.net/gif-speed-changer" rel="noopener noreferrer"&gt;LoopGIFâ€™s GIF Speed Changer&lt;/a&gt; for this. It is free, requires no sign-up, and runs in your browser; the GIF is not uploaded. You can apply a multiplier from Ã—0.25 to Ã—4, or set one fixed delay from 20 to 2,000 milliseconds. It accepts a GIF of up to 10 MB and 300 frames, keeps each frameâ€™s own delay when you use a multiplier, and will not write a delay below two hundredths. Delays of 0 or 1 in the source are read as ten, the way browsers play them. If a speed-up hits the floor, the tool reports how many frames were held back, and it shows the length and file size before and after. Those delays came from Pillow and the file bytes, not from this tool.&lt;/p&gt;

&lt;p&gt;For a pull-request GIF that flashes a message, start with Ã—0.5, and go to Ã—0.25 if the text is still hard to finish. To speed up a sluggish recording whose frames are already at two hundredths, you need fewer frames, not smaller delays.&lt;/p&gt;

&lt;p&gt;I build LoopGIF.&lt;/p&gt;

</description>
      <category>tutorial</category>
      <category>github</category>
      <category>webdev</category>
      <category>gif</category>
    </item>
    <item>
      <title>How to make a custom Slack emoji from a short GIF (and why a Discord export often fails)</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 10:44:51 +0000</pubDate>
      <link>https://dev.to/cicadasai/how-to-make-a-custom-slack-emoji-from-a-short-gif-and-why-a-discord-export-often-fails-3fag</link>
      <guid>https://dev.to/cicadasai/how-to-make-a-custom-slack-emoji-from-a-short-gif-and-why-a-discord-export-often-fails-3fag</guid>
      <description>&lt;p&gt;A Discord-ready reaction GIF is a reasonable starting point for a Slack workspace emoji, and a common reason the upload fails. Slack is not enforcing the same budget. A file that is slightly large, slightly long, slightly non-square, or in the wrong format will bounce, even if it already looks fine in another chat app.&lt;/p&gt;

&lt;p&gt;I build LoopGIF. The limits below come from Slack's own help article and API docs, which I fetched on 17 November 2026 (Asia/Shanghai). I also maintain a free browser tool that crops, flattens, and thins a clip for this job. Limits change; check Slack's current guidelines before you upload.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Slack actually publishes
&lt;/h2&gt;

&lt;p&gt;Slack's help article, &lt;a href="https://slack.com/help/articles/206870177-Add-custom-emoji-and-aliases-to-your-workspace" rel="noopener noreferrer"&gt;Add custom emoji and aliases to your workspace&lt;/a&gt;, is short on specs. The published guidance, quoted here, is:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Square images under 128KB and with transparent backgrounds work best. Images can be in JPG, PNG, or GIF format. GIFs can include up to 50 frames.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;128 KB is the size Slack tells you to aim for.&lt;/strong&gt; The wording is "work best," not a hard byte ceiling. Treat under 128 KB as the target. The Enterprise method &lt;a href="https://docs.slack.dev/reference/methods/admin.emoji.add" rel="noopener noreferrer"&gt;admin.emoji.add&lt;/a&gt; repeats the same "square images under 128KB" advice and can return &lt;code&gt;error_too_big&lt;/code&gt; when "the image file size is too large."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fifty frames is an explicit GIF cap.&lt;/strong&gt; The help article states it directly. The same API lists a &lt;code&gt;too_many_frames&lt;/code&gt; error: "The image has too many frames."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;JPG, PNG, and GIF only.&lt;/strong&gt; Slack does not list WebP or AVIF in that article. A file another service accepted in a different format is not a Slack emoji yet.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;No pixel size is published.&lt;/strong&gt; I searched the help article for a width or height and did not find one. "128 × 128" is a common convention, not a Slack requirement. Slack may resize a larger image. The API can also return &lt;code&gt;error_bad_wide&lt;/code&gt; ("the image width or height is too large") and &lt;code&gt;resized_but_still_too_large&lt;/code&gt;. Shape the square yourself so the crop stays under your control.&lt;/p&gt;

&lt;p&gt;Workspace Owners and Org Owners can restrict who may add custom emoji. The feature is available on all plans, with guests and Frontline Members excluded by default. A rejected upload is sometimes a permission problem, not a file problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a Discord-oriented export often fails here
&lt;/h2&gt;

&lt;p&gt;People reuse a Discord emoji file, or a README GIF cropped to a square, and expect Slack to take it.&lt;/p&gt;

&lt;p&gt;The file is over 128 KB. A Discord-oriented export is built for a looser size budget, so a 128 × 128 animated GIF that already "works" elsewhere can still sit well above Slack's published target.&lt;/p&gt;

&lt;p&gt;The GIF has more than 50 frames. Many reaction clips are two or three seconds at 24 or 30 frames per second — already 48–90 frames before you crop. Other chat pipelines have no reason to stop at 50, because that cap is Slack's rule.&lt;/p&gt;

&lt;p&gt;The format is not in Slack's list: WebP is a frequent leftover, and Slack names JPG, PNG, and GIF. Or the canvas is loose or huge. Slack may resize it, and a bad automatic crop can clip a face or leave empty background that wastes the 128 KB budget. An opaque white background, invisible in a light theme, becomes a white tile in Slack's dark theme.&lt;/p&gt;

&lt;h2&gt;
  
  
  Crop, flatten, then thin the frames
&lt;/h2&gt;

&lt;p&gt;An emoji is read at roughly the size of a line of chat text, and again as a small reaction. Crop to one subject: a face, a hand, a logo, a mascot.&lt;/p&gt;

&lt;p&gt;Because Slack does not publish a pixel size, pick a modest square and stay consistent. 128 × 128 is the size most tools default to, including mine. If the GIF still will not fit under 128 KB after you have flattened and thinned it, a smaller square can help, at the cost of a slightly softer picture. Those pixel sizes are a practical choice, not Slack's documented requirement.&lt;/p&gt;

&lt;p&gt;Slack says transparent backgrounds work best. The same emoji sits in a light composer, a dark sidebar, and a reaction pill. If your source is already a transparent GIF or PNG, keep that transparency. If it sits on a plain or near-plain colour, remove that colour so only the subject remains.&lt;/p&gt;

&lt;p&gt;GIF transparency is on or off, with no soft edges. A cut-out with fuzzy hair or a drop shadow will either halo or look jagged. A still PNG keeps those soft edges and has no frame budget to meet, so if the motion is not doing any work, ship a PNG.&lt;/p&gt;

&lt;p&gt;Then stay at or under 50 frames. Keep every second, third, or fourth frame, and add the delay of each dropped frame onto the frame you kept, so the loop lasts as long as it did instead of speeding up. After the frame cap, reduce the palette before you throw away more frames. Flat, graphic art compresses; camera grain, gradients, and a changing background do not. If you are still over 128 KB at 50 frames, thin further, tighten the crop, or drop to a still PNG.&lt;/p&gt;

&lt;p&gt;The fitting order that works is: square crop, optional background removal, cap at 50 frames with merged delays, then a smaller palette, then fewer frames, then a slightly smaller square if you must.&lt;/p&gt;

&lt;h2&gt;
  
  
  A browser pipeline that follows that order
&lt;/h2&gt;

&lt;p&gt;I built a &lt;a href="https://loopgif.net/slack-emoji-maker" rel="noopener noreferrer"&gt;Slack emoji maker&lt;/a&gt; for this last mile. It runs in your browser, with no sign-up, and the file is opened on your device and never uploaded. It accepts a GIF, a short video (MP4, MOV, or WebM), or a picture (PNG, JPG, or WebP), crops a square, keeps a transparent background where there is one, and can remove a plain background. It thins the animation to 50 frames or fewer by keeping every second, third, or fourth frame and merging delays, then tries to fit the file under 128 KB. You can export an animated GIF or a still PNG. The default size is 128 × 128; it also offers 96 and 64, which are the tool's sizes, not Slack's. After you press Make emoji, a checklist compares the result with the Slack figures the page last checked on 7 November 2026. The checklist is a guide; the upload is the final test.&lt;/p&gt;

&lt;p&gt;You do not need that tool to follow the steps above. Any editor that can crop a square, key a plain background, and thin frames with merged delays will do.&lt;/p&gt;

&lt;h2&gt;
  
  
  Names, and a last look before you upload
&lt;/h2&gt;

&lt;p&gt;When you add an emoji, Slack asks for a name. The admin.emoji.add docs say the name uses lower-case letters only, and the API can return &lt;code&gt;error_lower_case_names_only&lt;/code&gt; if you include capitals. I did not find a complete name grammar in the help article, so lower-case letters are the rule I can source.&lt;/p&gt;

&lt;p&gt;Preview the file small, on both a light and a dark background. If the motion stutters, shorten the clip or crop tighter rather than shipping a chopped loop. Then add it in the workspace, following the current steps in Slack's help article, if you have permission to do so.&lt;/p&gt;

&lt;p&gt;These figures were checked on 17 November 2026. Check the current guidelines before you upload.&lt;/p&gt;

&lt;p&gt;I build LoopGIF.&lt;/p&gt;

</description>
      <category>slack</category>
      <category>emoji</category>
      <category>gif</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Record a bug-repro GIF for a pull request that stays under GitHub's 10 MB limit</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 07:07:52 +0000</pubDate>
      <link>https://dev.to/cicadasai/record-a-bug-repro-gif-for-a-pull-request-that-stays-under-githubs-10-mb-limit-5dmm</link>
      <guid>https://dev.to/cicadasai/record-a-bug-repro-gif-for-a-pull-request-that-stays-under-githubs-10-mb-limit-5dmm</guid>
      <description>&lt;p&gt;A pull request that changes UI is much easier to review when the reviewer can &lt;em&gt;see&lt;/em&gt; the before and after. A short GIF does that inline: it loops in the PR description, it needs no click, and it also works in places where video does not play.&lt;/p&gt;

&lt;p&gt;The catch is size. GitHub's documentation lists a &lt;strong&gt;10 MB maximum for images and GIFs&lt;/strong&gt; attached to issues, pull requests and comments (check the current "Attaching files" page; limits change). A careless 30-second full-screen recording blows past that easily. This walkthrough records a short clip, trims it, and checks the file before you drag it into the PR.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Disclosure: I work with the team behind LoopGIF, and the recorder used below is LoopGIF's free browser tool. AI assistance was used to draft this post; the steps and the script were checked by hand. Any recorder works — the size rules are the same.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  1. Decide what the GIF has to prove
&lt;/h2&gt;

&lt;p&gt;Before you record, write one sentence: &lt;em&gt;"Clicking Save with an empty title shows the inline error instead of a toast."&lt;/em&gt; If the GIF needs more than one sentence, it probably needs two GIFs (before / after) rather than one long one.&lt;/p&gt;

&lt;p&gt;Practical limits that keep files small:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;One interaction per clip.&lt;/strong&gt; Reviewers scan; 5–10 seconds is usually enough.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Record a region or a single tab, not the whole screen.&lt;/strong&gt; Pixel area is the biggest driver of GIF size.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;10–12 fps is plenty for UI.&lt;/strong&gt; Clicks and form errors don't need 30 fps.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  2. Record the clip in the browser
&lt;/h2&gt;

&lt;p&gt;Open the &lt;a href="https://loopgif.net/screen-recording-to-gif" rel="noopener noreferrer"&gt;LoopGIF screen recording to GIF tool&lt;/a&gt;. It runs in a desktop browser and uses the browser's own "share a tab, window or screen" prompt; the page says the recording stays in the tab and nothing is uploaded.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Pick a frame rate: 10, 12 or 15 fps. The recorder stops by itself at 300 frames (30 s at 10 fps, 25 s at 12 fps, 20 s at 15 fps).&lt;/li&gt;
&lt;li&gt;Press &lt;strong&gt;Start recording&lt;/strong&gt; and choose the &lt;strong&gt;tab&lt;/strong&gt; that shows your app — sharing a single tab instead of the whole screen keeps the frame small and avoids leaking other windows.&lt;/li&gt;
&lt;li&gt;Reproduce the bug once, then press &lt;strong&gt;Stop&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;No audio is captured, which is what you want for a PR anyway.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Trim and size it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Drag the &lt;strong&gt;start&lt;/strong&gt; and &lt;strong&gt;end&lt;/strong&gt; sliders so the clip starts one beat before the click and ends right after the result appears. Every idle second you cut is bytes saved.&lt;/li&gt;
&lt;li&gt;Choose a &lt;strong&gt;width&lt;/strong&gt;. GitHub's PR column is far narrower than a 1440 px screen, so a 640 px wide GIF still reads clearly.&lt;/li&gt;
&lt;li&gt;Choose &lt;strong&gt;Balanced&lt;/strong&gt; for crisp UI text, or &lt;strong&gt;Smaller file&lt;/strong&gt; if you are near the limit.&lt;/li&gt;
&lt;li&gt;Press &lt;strong&gt;Create GIF&lt;/strong&gt;. The tool shows the size, frame count and length of the result before you download it.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  4. Check the file before you upload
&lt;/h2&gt;

&lt;p&gt;If you want a quick sanity check (or you are adding GIFs in CI docs), this script prints what matters. It needs Python 3 and Pillow (&lt;code&gt;pip install pillow&lt;/code&gt;):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="c1"&gt;# check_pr_gif.py&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;sys&lt;/span&gt;
&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;pathlib&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Path&lt;/span&gt;
&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="no"&gt;PIL&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Image&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;ImageSequence&lt;/span&gt;

&lt;span class="no"&gt;LIMIT&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;1024&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;1024&lt;/span&gt;  &lt;span class="c1"&gt;# GitHub: 10MB for images and gifs (check current docs)&lt;/span&gt;

&lt;span class="n"&gt;path&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Path&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;sys&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;argv&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;with&lt;/span&gt; &lt;span class="nc"&gt;Image&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nb"&gt;open&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;path&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;im&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;durations&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;info&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"duration"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;f&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="nc"&gt;ImageSequence&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Iterator&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;im&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="n"&gt;width&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;height&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;im&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;size&lt;/span&gt;

&lt;span class="n"&gt;size&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;path&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stat&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;st_size&lt;/span&gt;
&lt;span class="n"&gt;total_ms&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;sum&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;durations&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"{width}x{height}px, {len(durations)} frames, {total_ms/1000:.1f}s"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"{size/1024/1024:.2f} MB of {LIMIT/1024/1024:.0f} MB"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;size&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="no"&gt;LIMIT&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Too big: trim the clip, lower the width, or use 'Smaller file'."&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;sys&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;exit&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python check_pr_gif.py save-error.gif
&lt;span class="c"&gt;# 640x400px, 72 frames, 7.2s   (example output; your numbers will differ)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  5. Put it in the PR
&lt;/h2&gt;

&lt;p&gt;Drag the GIF into the PR description. GitHub uploads it and inserts the Markdown for you. Then add alt text that says what happens, because "demo" tells a screen-reader user nothing:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gs"&gt;**Before**&lt;/span&gt; — empty title shows a toast that disappears:
![Clicking Save with an empty title shows a toast that vanishes after 2 seconds](before.gif)

&lt;span class="gs"&gt;**After**&lt;/span&gt; — the error stays next to the field:
![Clicking Save with an empty title shows an inline error under the Title field](after.gif)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  When a GIF is the wrong choice
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Longer than ~30 seconds, or you need audio:&lt;/strong&gt; attach an MP4 instead. GitHub plays videos inline in PRs (10 MB on free plans, 100 MB on paid plans, per the same docs page).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Photo-like content (video calls, camera footage):&lt;/strong&gt; GIF's 256-colour palette makes these large and blotchy; MP4 is better.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;README demos that must also show on npm or a docs site:&lt;/strong&gt; a GIF committed to the repo is still the most portable option.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] One interaction, 5–10 s&lt;/li&gt;
&lt;li&gt;[ ] Single tab or region, ~640 px wide&lt;/li&gt;
&lt;li&gt;[ ] 10–12 fps&lt;/li&gt;
&lt;li&gt;[ ] Under 10 MB (check before uploading)&lt;/li&gt;
&lt;li&gt;[ ] Alt text that describes the behaviour&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>tutorial</category>
      <category>github</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Make a Typing GIF for a README and Check Its Timing</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 05:18:43 +0000</pubDate>
      <link>https://dev.to/cicadasai/make-a-typing-gif-for-a-readme-and-check-its-timing-4e15</link>
      <guid>https://dev.to/cicadasai/make-a-typing-gif-for-a-readme-and-check-its-timing-4e15</guid>
      <description>&lt;p&gt;A typing GIF can show a short build message or command without asking a reader to play a video. The useful part is not the animation alone: the text needs enough time to be read, the file needs to be small, and the loop should behave as you expect in the place where you embed it.&lt;/p&gt;

&lt;p&gt;This walkthrough makes a small terminal-style example and checks the exported GIF with Python. The exact frame count and file size depend on the message and settings you choose.&lt;/p&gt;

&lt;h2&gt;
  
  
  Create the typing animation
&lt;/h2&gt;

&lt;p&gt;Open &lt;a href="https://loopgif.net/typing-text-gif-maker" rel="noopener noreferrer"&gt;LoopGIF's typing text GIF maker&lt;/a&gt;. I work with the team behind LoopGIF; AI assistance was used to draft this tutorial. The page describes this particular editor as free and says it renders the GIF in the browser.&lt;/p&gt;

&lt;p&gt;For the example, use these settings:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Enter &lt;code&gt;BUILD COMPLETE&lt;/code&gt; as the text.&lt;/li&gt;
&lt;li&gt;Start with the Terminal style and leave the canvas at 480 × 270.&lt;/li&gt;
&lt;li&gt;Set the typing speed to 12 characters per second and the end hold to 1.5 seconds.&lt;/li&gt;
&lt;li&gt;Select the block cursor, enable its blink, and enable &lt;strong&gt;Delete and retype&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Check the preview, then choose &lt;strong&gt;Download GIF&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;In the test export, the page reported 30 frames, approximately 3.1 seconds and an estimated size of 25 KB. The downloaded file measured 26,774 bytes. Those are measurements of this example, not a promise for every export.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the exported GIF with Python
&lt;/h2&gt;

&lt;p&gt;If you have Python and Pillow installed, save this as &lt;code&gt;inspect_gif.py&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;sys&lt;/span&gt;
&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;pathlib&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Path&lt;/span&gt;

&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="no"&gt;PIL&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Image&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;ImageChops&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;ImageSequence&lt;/span&gt;

&lt;span class="n"&gt;path&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Path&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;sys&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;argv&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;with&lt;/span&gt; &lt;span class="nc"&gt;Image&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nb"&gt;open&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;path&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;image&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;size&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;image&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;size&lt;/span&gt;
    &lt;span class="n"&gt;loop&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;image&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;info&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"loop"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;frames&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="n"&gt;durations&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;frame&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="nc"&gt;ImageSequence&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Iterator&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;image&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="n"&gt;durations&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;frame&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;info&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"duration"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
        &lt;span class="n"&gt;frames&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;frame&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;convert&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"RGB"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;copy&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

    &lt;span class="n"&gt;difference&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;ImageChops&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;difference&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;frames&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;frames&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getbbox&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"Size: {size[0]} × {size[1]}"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"Frames: {len(frames)}"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"Total duration: {sum(durations)} ms"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"Loop value: {loop}"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"First/last difference: {difference}"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"File size: {path.stat().st_size} bytes"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run &lt;code&gt;python inspect_gif.py path/to/typing-text.gif&lt;/code&gt;. If Pillow is missing, install it in the Python environment you use for this check: &lt;code&gt;python -m pip install Pillow&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;For this file, Pillow reported 480 × 270, 30 frames, 3,140 ms and a loop value of &lt;code&gt;0&lt;/code&gt;, which means infinite looping in the GIF. The first and last frames differed in a small rectangle. That does &lt;strong&gt;not&lt;/strong&gt; by itself mean the animation is broken: a blinking cursor or a letter appearing at the loop boundary can create a difference. Watch the exported file in its intended viewer before deciding whether the transition is acceptable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make the result easier to read
&lt;/h2&gt;

&lt;p&gt;Keep the message short enough to fit without shrinking it to an unreadable size. Use the hold setting to give readers time to see the completed line. If the ending feels abrupt, try a longer hold, turn off cursor blinking, or compare a version with &lt;strong&gt;Delete and retype&lt;/strong&gt; disabled. Export each variant and check the result; a slower animation is not automatically a smaller file.&lt;/p&gt;

&lt;p&gt;For a transparent background, test it on the actual page color. GIF transparency is binary, so the edge color used around text can show as a halo on a contrasting background. The editor explains this limitation in its on-page notes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Add it to a README
&lt;/h2&gt;

&lt;p&gt;If the hosting service supports animated GIFs in Markdown, add the exported file to your project and reference it with a relative path:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;![A terminal message typing BUILD COMPLETE](./assets/build-complete.gif)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Open the rendered README and verify that the animation plays, the text is legible and the file path is correct. Some viewers reduce or disable animation, so keep important instructions in ordinary text as well.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Does the animation have to loop forever?
&lt;/h3&gt;

&lt;p&gt;No. Choose the loop behavior that fits the destination. The example above uses the editor's infinite-loop setting.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why does the final file size differ from the preview?
&lt;/h3&gt;

&lt;p&gt;The displayed size is an estimate. The exported GIF has its own measured size, which can change with dimensions, colors and frame content.&lt;/p&gt;

&lt;h3&gt;
  
  
  Are matching first and last frames required?
&lt;/h3&gt;

&lt;p&gt;Not always. They are a useful diagnostic for a visually continuous loop, but an intentional cursor blink or typing transition may differ. Inspect the animation rather than treating the pixel comparison as a pass-or-fail quality score.&lt;/p&gt;

&lt;h3&gt;
  
  
  What should I put in the alt text?
&lt;/h3&gt;

&lt;p&gt;Describe the information the animation conveys. A screen reader does not need a frame-by-frame account of a decorative cursor.&lt;/p&gt;

</description>
      <category>python</category>
      <category>tutorial</category>
      <category>gif</category>
      <category>readme</category>
    </item>
    <item>
      <title>How to Get an Editable Caption File From a Public Short-Form Video</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Sat, 14 Nov 2026 01:53:43 +0000</pubDate>
      <link>https://dev.to/cicadasai/how-to-get-an-editable-caption-file-from-a-public-short-form-video-5h09</link>
      <guid>https://dev.to/cicadasai/how-to-get-an-editable-caption-file-from-a-public-short-form-video-5h09</guid>
      <description>&lt;p&gt;&lt;strong&gt;Disclosure:&lt;/strong&gt; I work on ClipScript, a short-form transcription tool. This article is about getting a caption file you can actually edit. The workflow below does not require that tool.&lt;/p&gt;

&lt;p&gt;You need the spoken words from a short video as text: a quote, a translation, a subtitle file, or a script you can search. The usual in-app captions do not give you that. They appear a line at a time over the picture, and you cannot select them, copy them, or download a file.&lt;/p&gt;

&lt;p&gt;What you want is an &lt;code&gt;.srt&lt;/code&gt; or &lt;code&gt;.vtt&lt;/code&gt; file: one cue per line, each with a start and end time, that an editor or YouTube Studio can import.&lt;/p&gt;

&lt;h2&gt;
  
  
  First, decide whether you have the file or only a link
&lt;/h2&gt;

&lt;p&gt;If the video is yours, start from the file. You already have the audio. Upload or drop it into an editor or a transcriber that exports SRT or VTT, then edit the cues before you burn anything into the picture.&lt;/p&gt;

&lt;p&gt;If the video is a public Instagram Reel, TikTok, Short, or similar post, you often have only a share link. The app may show captions, but it still will not export a transcript. In that case you need a step that can read a public link and return timed text.&lt;/p&gt;

&lt;p&gt;A link-based run only works when anyone can open the post without signing in. Private accounts, Close Friends, and expired Stories do not have a lasting public URL you can transcribe. A failed run on a removed or private post should not be treated as a usable result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Speech is not the same as text on screen
&lt;/h2&gt;

&lt;p&gt;A transcript is what is said, not what is written in the frame. A recipe that appears only as on-screen type, with music underneath and no voiceover, has nothing reliable to transcribe. Songs are also a poor fit: you may get some lyrics, but models built for speech will miss or invent words.&lt;/p&gt;

&lt;p&gt;If the words you actually need are in the picture, pause and type them, or use a still-frame workflow. Do not expect a speech transcript to recover them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the file before you import it
&lt;/h2&gt;

&lt;p&gt;Auto captions are a draft. Before you publish or quote from them, play the video with the SRT open and check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Proper nouns, product names, and places&lt;/li&gt;
&lt;li&gt;Numbers, prices, and times&lt;/li&gt;
&lt;li&gt;The first one or two seconds, which often start over music or a hook&lt;/li&gt;
&lt;li&gt;Overlapping talk and background noise&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If a line is wrong, fix it in the caption file. That is cheaper than correcting a burned-in subtitle later.&lt;/p&gt;

&lt;p&gt;Timed formats help here. Plain text is fine for a quote. SRT or VTT is what you want when the words have to stay aligned with the picture.&lt;/p&gt;

&lt;h2&gt;
  
  
  Import the file, then decide whether to burn it in
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;YouTube Studio:&lt;/strong&gt; upload the SRT or VTT as a caption track so viewers can turn it on or off.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CapCut and similar editors:&lt;/strong&gt; import the caption file, nudge cues that drift, and only then burn them into the picture if you need them always visible.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Premiere or Resolve:&lt;/strong&gt; import the captions as a caption item, not as a title you retype by hand.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Burned-in captions are a design choice for sound-off viewing. A separate caption file is the one you can still correct after upload.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you only have a public link
&lt;/h2&gt;

&lt;p&gt;The checks above work with a desktop editor or any transcriber that returns an SRT. If you mainly need timed text from a public Instagram Reel, I also maintain a free link-based path at &lt;a href="https://clipscript.app/instagram-transcript" rel="noopener noreferrer"&gt;ClipScript&lt;/a&gt;. It is not required for this workflow. Three short public runs a day are free without an account; private posts and Stories will not work, and on-screen text is not speech.&lt;/p&gt;

&lt;p&gt;Once you have the file, the useful work is the same: correct the cues, then import them.&lt;/p&gt;

</description>
      <category>video</category>
      <category>tutorial</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How to Loop a Short Video Without an Obvious Jump or Audio Click</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Sat, 14 Nov 2026 01:37:42 +0000</pubDate>
      <link>https://dev.to/cicadasai/how-to-loop-a-short-video-without-an-obvious-jump-or-audio-click-i06</link>
      <guid>https://dev.to/cicadasai/how-to-loop-a-short-video-without-an-obvious-jump-or-audio-click-i06</guid>
      <description>&lt;p&gt;The join is the edit. Review it separately from the attractive part in the middle.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Disclosure:&lt;/strong&gt; I founded Cicadas, an AI video service. This article was revised with AI writing assistance, as was the original tutorial. The existing demonstration listed under Sources uses AI-generated kinetic-sand footage and a browser-tool export. It is illustrative footage, not a new comparison test or proof that every clip can loop seamlessly.&lt;/p&gt;

&lt;p&gt;A loop has two boundaries to solve: the picture must return to a plausible starting point, and the sound must restart without calling attention to itself. Repeating a file does not solve either one. Sometimes a plain cut works. Sometimes a blend helps. Sometimes the footage is better left as a short, non-looping shot.&lt;/p&gt;

&lt;p&gt;You can follow the workflow below in an editor that supports trimming and duplication. Crossfades and separate audio editing are optional, not prerequisites for a useful first check.&lt;/p&gt;

&lt;p&gt;The checks below work in a traditional editor or a browser tool. If you mainly need to repeat a short clip a few times and optionally blend the join while keeping the soundtrack, I also maintain a free in-browser looper at &lt;a href="https://cicadas.ai/loop-video" rel="noopener noreferrer"&gt;Cicadas.ai&lt;/a&gt;. It is not required for this workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  First, decide what “loop” means for this delivery
&lt;/h2&gt;

&lt;p&gt;A &lt;strong&gt;player loop&lt;/strong&gt; restarts one file when playback reaches the end. A &lt;strong&gt;repeated export&lt;/strong&gt; puts several copies of a segment inside one longer file. If you need a longer upload, you need the latter; a repeat button in a preview player does not create it.&lt;/p&gt;

&lt;p&gt;Write down the target length, crop, and whether sound matters. A silent website background and an ASMR post need different tests. Also ask whether the destination will loop the whole exported file: that creates an outer boundary as well as the joins you edit inside it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Find a restart the viewer can believe
&lt;/h2&gt;

&lt;p&gt;Place the final frame beside the first. Compare the camera position, subject position, lighting, and direction of motion. Similar poses help, but the movement into and out of those poses matters too.&lt;/p&gt;

&lt;p&gt;Try a segment with stable framing and a small repeatable movement. Trim opening hesitation, end cards, and abrupt entrances or exits. Do not trim so tightly that the action no longer makes sense.&lt;/p&gt;

&lt;p&gt;Irreversible actions need a different expectation. In the existing sand example, a cut is followed by a reset to uncut material on repetition. A crossfade can soften that reset, but it cannot make the material physically continuous. You can accept a visibly repeated demonstration, choose a quieter section, or decide not to loop it. Those are editorial choices, not failures to find the right button.&lt;/p&gt;

&lt;h2&gt;
  
  
  Expose the seam with a plain cut
&lt;/h2&gt;

&lt;p&gt;Duplicate the chosen segment a few times with no transition. Watch across each join, not just the action inside each copy.&lt;/p&gt;

&lt;p&gt;As a simple exercise—not a reported export test—repeat a four-second segment three times. Without overlap, the expected duration is about twelve seconds. Compare that expectation with the saved file. A different result is a reason to check trims or transition behavior.&lt;/p&gt;

&lt;p&gt;If the plain join looks natural, stop there. A blend is not automatically more polished; it can soften crisp edges or create two copies of an object.&lt;/p&gt;

&lt;p&gt;If the join jumps, identify what jumps. A changed camera position suggests trying a different segment. A hand in incompatible poses may need different trim points. A small change in light may be less distracting than a long ghosted transition.&lt;/p&gt;

&lt;h2&gt;
  
  
  Blend only if the overlap improves this boundary
&lt;/h2&gt;

&lt;p&gt;If your editor supports it, add a short crossfade and compare the same join with and without it. Watch clear edges: a knife, hand, cup rim, or face. Two visible outlines may be more distracting than the original cut.&lt;/p&gt;

&lt;p&gt;Adjust the overlap by looking at the result, not by choosing a supposedly universal duration. The useful length depends on the movement. Keep the plain-cut version so you can make a direct comparison.&lt;/p&gt;

&lt;p&gt;Overlapping footage can shorten the export. Do not assume that segment length multiplied by repetition count still gives the delivery length. Read the actual duration and trim or extend deliberately if the destination requires an exact length.&lt;/p&gt;

&lt;h2&gt;
  
  
  Listen to at least three joins without watching
&lt;/h2&gt;

&lt;p&gt;A smooth visual blend can hide a sharp sound restart. At a comfortable volume, listen for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a click at the boundary;&lt;/li&gt;
&lt;li&gt;an impact or word cut in half;&lt;/li&gt;
&lt;li&gt;a sudden change in background noise;&lt;/li&gt;
&lt;li&gt;a rhythm that stumbles on every repetition.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Move the trim point into a quieter moment if possible. Speech and rhythmic music can make a seam obvious even when the picture is forgiving. If needed, edit the sound separately: try a small fade, or use a continuous ambience track you have permission to publish. Listen again; a fade can remove a click while making the volume dip conspicuously.&lt;/p&gt;

&lt;p&gt;Confirm that the saved file actually contains the intended audio. A browser preview with sound is not proof that the exported file has it. If it is unexpectedly silent, check export settings and any encoder warning before changing the visual edit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use reverse playback deliberately
&lt;/h2&gt;

&lt;p&gt;Forward-then-backward playback can suit swaying or a gentle turn. It is not the same effect as repeating motion in one direction.&lt;/p&gt;

&lt;p&gt;With pouring or cutting, reverse playback makes liquid flow upward or a cut rebuild itself. That may be the intended effect, but it is not a natural continuation. Handle the audio separately rather than accidentally reversing a voice or impact with the picture.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the file, then test its final restart
&lt;/h2&gt;

&lt;p&gt;Open the exported video outside the editing tool. Check crop, duration, sound, and all internal joins. If the destination repeats the entire file, play it on repeat and examine the last frame meeting the first. Smooth joins inside the export do not establish that the outer boundary is smooth.&lt;/p&gt;

&lt;p&gt;Keep a note of the source, trim points, repetition count, and blend setting. If you hear a problem later, those notes let you repair the boundary instead of rebuilding the edit from memory.&lt;/p&gt;

&lt;p&gt;The goal is not to hide repetition at any cost. It is to make sure the restart does not undermine the scene. When a loop requires distracting ghosting or an implausible reversal, a clean ending may be the better edit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://www.youtube.com/watch?v=QWTgbP11bcU" rel="noopener noreferrer"&gt;Existing kinetic-sand loop demonstration&lt;/a&gt; — the first-party Cicadas demonstration embedded in the original article; AI-generated footage with sound and a browser-tool export. Retained as an editing example, not an independent endorsement.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>video</category>
      <category>tutorial</category>
      <category>editing</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to Plan AI Video Shots Without Burning Credits on Retries</title>
      <dc:creator>Cicadas.ai</dc:creator>
      <pubDate>Thu, 29 Oct 2026 00:33:11 +0000</pubDate>
      <link>https://dev.to/cicadasai/how-to-plan-ai-video-shots-without-burning-credits-on-retries-417h</link>
      <guid>https://dev.to/cicadasai/how-to-plan-ai-video-shots-without-burning-credits-on-retries-417h</guid>
      <description>&lt;p&gt;&lt;strong&gt;Subtitle:&lt;/strong&gt; A practical workflow for text-to-video and image-to-video: lock framing first, quote cost before generate, and treat failed jobs as a process check—not a surprise bill.&lt;/p&gt;




&lt;p&gt;AI video tools are fast enough that the expensive part is rarely “waiting for a render.” It is the quiet pile of retries: wrong motion, wrong framing, an image that drifts, or a five-second clip that looks fine in the thumbnail and unusable at full size. If you create short-form content, product demos, or social trend formats, a small planning habit beats buying more credits later.&lt;/p&gt;

&lt;p&gt;This article is a concrete how-to for text-to-video and image-to-video. It does not rank models or invent usage stats. It focuses on decisions you can make before you press generate.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Decide the job type before you write a prompt
&lt;/h2&gt;

&lt;p&gt;Treat “AI video” as at least three different jobs:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Text-to-video&lt;/strong&gt; — you describe a scene; the model invents motion, camera, and often lighting.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Image-to-video&lt;/strong&gt; — you supply a still (product photo, portrait, key art); the model adds motion while trying to keep identity and layout.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Named social formats&lt;/strong&gt; — hug videos, birthday candles, talking pets, “meet older self,” and similar recipes that start from your photo or a short prompt.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Mixing these in one session is fine. Mixing them in one prompt usually is not. If you already have a product shot you like, start from image-to-video. If you need a completely new environment, start from text-to-video. If you want a recognizable trend format, use that tool’s defaults first and only then customize.&lt;/p&gt;

&lt;p&gt;Write one sentence that names the deliverable: “5-second vertical product pan with soft studio light” or “warm park hug, two people, camera locked.” That sentence becomes your acceptance test later.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Lock framing on stills before you spend on motion
&lt;/h2&gt;

&lt;p&gt;Motion models amplify framing mistakes. A subject cut at the elbows, a logo too close to the edge, or a busy background will look worse once the camera “breathes.”&lt;/p&gt;

&lt;p&gt;Before any paid motion run:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Crop the source image to the aspect ratio you will publish (9:16 for Reels/TikTok, 16:9 for YouTube, 1:1 for some feeds).&lt;/li&gt;
&lt;li&gt;Leave safe margins around faces and logos.&lt;/li&gt;
&lt;li&gt;Remove objects you do not want the model to invent motion for (reflections, clutter, another person’s hand).&lt;/li&gt;
&lt;li&gt;If the still is soft or noisy, upscale or clean it first; motion rarely fixes a soft source.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For text-to-video, sketch the same constraints in text: subject size in frame, camera height, what must stay still. One useful pattern:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Subject and action · camera move (or locked) · light and style · what must not change · what to avoid&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Example: “Ceramic mug on oak table, slow push-in, soft window light, keep logo readable, no people, no text overlays.”&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Prefer short test clips, then scale length
&lt;/h2&gt;

&lt;p&gt;Most creators over-buy length on the first try. A five-second test is enough to check identity drift, camera path, and whether the model respects your “do not change” list. If the five-second clip fails those checks, a ten-second clip will usually fail the same way—at a higher cost.&lt;/p&gt;

&lt;p&gt;Practical sequence:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Generate the shortest useful length your tool allows.&lt;/li&gt;
&lt;li&gt;Watch it muted once for composition, then with audio if the model includes sound.&lt;/li&gt;
&lt;li&gt;Only after framing and identity look stable, increase length or resolution.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If your tool quotes credits by model, length, resolution, and sound, treat that quote as part of the creative brief. Change one variable at a time so you know what the cost change bought you.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Write prompts for motion, not for still photography
&lt;/h2&gt;

&lt;p&gt;Still-image prompt habits (“masterpiece, 8k, intricate details”) waste budget in video. Prefer verbs, camera language, and continuity:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Verbs:&lt;/strong&gt; walk, turn, blink, pour, hug, wind moves hair.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Camera:&lt;/strong&gt; locked tripod, slow dolly in, gentle orbit, handheld micro-shake (only if you want it).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Continuity:&lt;/strong&gt; same outfit, same logo, same background, keep face identity.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For image-to-video, say what should move and what should stay. “Subtle smile and slight head turn; keep hair color, clothing, and background fixed” is clearer than a paragraph of style adjectives.&lt;/p&gt;

&lt;p&gt;Negative guidance helps when the model invents extras: no morphing hands, no extra fingers, no text in the frame, no sudden zoom.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Budget like a producer: quote first, confirm once
&lt;/h2&gt;

&lt;p&gt;Credit-based studios differ from flat “unlimited” plans. The useful property is visibility: you should see how many credits a specific model, length, and resolution will use &lt;strong&gt;before&lt;/strong&gt; the job starts.&lt;/p&gt;

&lt;p&gt;On &lt;a href="https://cicadas.ai" rel="noopener noreferrer"&gt;Cicadas.ai&lt;/a&gt;, for example, each generation shows its credit price up front, and nothing is charged until you confirm. Failed jobs (provider failures or results that fail their checks) return those credits automatically. Successful clips you simply dislike still cost credits—so the planning steps above matter more than hoping for a refund on taste.&lt;/p&gt;

&lt;p&gt;Use that model wherever you work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Read the quote when you change duration or resolution.&lt;/li&gt;
&lt;li&gt;Keep a simple log: date, tool/model, length, credits quoted, pass/fail reason.&lt;/li&gt;
&lt;li&gt;Separate “technical fail” (black frame, crash, empty output) from “creative miss” (wrong vibe). Only the first should feel like a billing issue.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you are exploring trend formats, a deep link such as &lt;a href="https://cicadas.ai/ai-hug-video-generator" rel="noopener noreferrer"&gt;Cicadas.ai’s AI Hug Video Generator&lt;/a&gt; is a good place to learn defaults before you rebuild the same shot from a blank text prompt.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. A one-hour workflow you can repeat
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Minutes 0–15 — Brief&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Write the one-sentence deliverable, pick aspect ratio, gather or shoot the source stills.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Minutes 15–25 — Still prep&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Crop, clean, remove distractors. Export the exact file you will feed the model.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Minutes 25–40 — Short motion tests&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Two or three short image-to-video or text-to-video runs. Change only one prompt line between them. Record the credit quote each time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Minutes 40–50 — Review&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Pass/fail against the brief: identity, logo, camera, length. Drop anything that fails framing; do not “fix it with a longer clip.”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Minutes 50–60 — Final length or format&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Only the winners get a longer render, higher resolution, or a named social format pass. Export, caption offline if needed, and archive the prompt + settings with the MP4.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Common failure modes and cheap fixes
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Symptom&lt;/th&gt;
&lt;th&gt;Likely cause&lt;/th&gt;
&lt;th&gt;Cheaper fix&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Face morphs mid-clip&lt;/td&gt;
&lt;td&gt;Weak identity lock / over-aggressive motion&lt;/td&gt;
&lt;td&gt;Shorter clip; softer verbs (“slight smile” not “dance”)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Logo warps&lt;/td&gt;
&lt;td&gt;Too close to edge or low-res source&lt;/td&gt;
&lt;td&gt;Recrop with margins; sharper still&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Random text in frame&lt;/td&gt;
&lt;td&gt;Model inventing signage&lt;/td&gt;
&lt;td&gt;Explicit “no text, no logos except the product mark”&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Useless camera swirl&lt;/td&gt;
&lt;td&gt;Prompt implied cinematic energy&lt;/td&gt;
&lt;td&gt;Specify “locked camera” or “slow push-in only”&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Good still, bad motion&lt;/td&gt;
&lt;td&gt;Wrong job type&lt;/td&gt;
&lt;td&gt;Switch from text-to-video to image-to-video&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  8. What not to optimize for
&lt;/h2&gt;

&lt;p&gt;Skip vanity metrics in your planning notes. You do not need public “top model” rankings to ship a usable five-second ad. You need a brief, a framed still, a short test, and a clear credit quote. If a platform shows exact cost before run and restores credits on failed generations, use that information the same way you would use a print shop’s proof price: confirm once, then print.&lt;/p&gt;

&lt;h2&gt;
  
  
  Closing checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] One-sentence deliverable written
&lt;/li&gt;
&lt;li&gt;[ ] Aspect ratio and source crop locked
&lt;/li&gt;
&lt;li&gt;[ ] Prompt uses verbs + camera + “must not change”
&lt;/li&gt;
&lt;li&gt;[ ] First tests are shortest useful length
&lt;/li&gt;
&lt;li&gt;[ ] Credit quote read before confirm
&lt;/li&gt;
&lt;li&gt;[ ] Failures logged as technical vs creative
&lt;/li&gt;
&lt;li&gt;[ ] Only winners get longer / higher-res runs
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Plan the shot, pay for the motion you actually need, and keep retries intentional. That is the difference between AI video as a toy and AI video as a weekly production habit.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>tutorial</category>
      <category>machinelearning</category>
    </item>
  </channel>
</rss>
