>>189069

KEKMAKER 5000 fag here. Protip: when making GIFs, first make them as a video, then convert them with ffmpeg, it's much more suited for creating GIFs with palletes-per-frame, cheating with transparency to only update parts of the screen and other size-optimization techniques that would make this GIF a much more managable size. Here's a command that would start you off:

ffmpeg -v warning -i "INPUT FILE" -lavfi "palettegen=stats_mode=single[pal],[0:v][pal]paletteuse=new=1" -gifflags +transdiff -y OUTPUT.gif

>>189125

For best results, uncompressed RGB or non-lossy compressed, ffmpeg will understand the input. If you need a binary, there are zeranoe's builds available here https:// ffmpeg.zeranoe.com/builds/

>>189138

1024x512 is fine for this particular GIF I think, but the smaller the canvas, the better the results. Also keep in mind Twitter is converting uploaded GIFs into mp4 for viewing inside the page, so if you have good upload, don't worry about the final size. Size optimizations matter most when uploading the GIF elsewhere (like here, but don't worry, 16MB is the current file size limit on 8ch)

>>189140

I'd try to keep it under 3MB, so you're already there, it's just possible to get there with less of a size and a better visual result.