01
Why most GIF signatures break.
A GIF made the obvious way starts from nothing: a blank frame, then the photo or logo wiping in. In a client that animates, that is fine. In a client that shows only the first frame, the reader sees an empty box where your face should be, for ever.
The fix is to rotate the animation so frame one is the finished picture, and let the motion happen after it. Every GIF the generator makes is built that way from the start.
02
Made from your own photo.
You do not need to make a GIF yourself. Upload a photo, and the generator renders it through the design's own motion in your browser: a light sweeping across it, a wipe, an oval opening, three pills assembling into your face. Each design has one motion of its own, and 9 motions are used across the designs.
The GIF is drawn at twice the size it is shown, so it stays sharp on a phone's screen.
03
How big a signature GIF should be.
Small. Every animation is held to a byte budget of 250KB, and a whole signature, photo, logo and icons together, comes to about a quarter of a megabyte. Bigger files load slowly on a phone, and some corporate mail filters treat heavy images with suspicion.
The motion is short too: a rest, then a fraction of a second of movement, then a rest again. A signature that loops constantly distracts from the email above it.
04
Hosted, not attached.
A GIF pasted into some mail clients becomes an attachment, with a paperclip on every email you send. The generator hosts every image instead, so your signature references it by address and nothing is attached.
05
Text stays text.
Only the photo, logo and icons are images. Your name, role, phone and links are real text, so the signature still reads when images are blocked and a screen reader can read it aloud. A signature that is one GIF has none of that.

