Make a GIF faster or slower by changing the delay between frames. Drag the speed slider and watch the preview change live; for very high speeds GifCraft drops frames instead of setting delays browsers would ignore.
Drop the GIF.
Set a speed between 0.25× and 4×.
Make the GIF.
GIF delays are stored in hundredths of a second. Browsers treat delays of 0 or 1 hundredths (10 ms or less) as broken and slow them down to 100 ms, which makes an over-sped GIF suddenly crawl. GifCraft never writes a delay below 20 ms; above that speed it drops frames. The frame-timing explainer on the guide page shows it.
A GIF has no frame rate. Each frame carries its own delay, stored as a whole number of hundredths of a second. That has two surprising effects: only some frame rates are exact, and delays that are too short get slowed down by browsers.
Rates that divide 100 evenly — 50, 25, 20, 12.5, 10 — play exactly. 30 fps becomes 3/100 s, which is really 33.3 fps; 15 fps becomes 7/100 s (14.3 fps). Over a 3-second loop these drifts are invisible, but they explain why a converted clip can end a little early or late.
No. The GIF is decoded, edited and re-encoded inside your browser. Nothing is sent to a server, so there is no account, no queue and no watermark.
Its frame delay is probably 0 or 10 ms, which browsers clamp to 100 ms. Re-save it here and GifCraft rewrites the timing properly.