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.
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.
What Slack actually publishes
Slack's help article, Add custom emoji and aliases to your workspace, is short on specs. The published guidance, quoted here, is:
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.
128 KB is the size Slack tells you to aim for. The wording is "work best," not a hard byte ceiling. Treat under 128 KB as the target. The Enterprise method admin.emoji.add repeats the same "square images under 128KB" advice and can return error_too_big when "the image file size is too large."
Fifty frames is an explicit GIF cap. The help article states it directly. The same API lists a too_many_frames error: "The image has too many frames."
JPG, PNG, and GIF only. 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.
No pixel size is published. 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 error_bad_wide ("the image width or height is too large") and resized_but_still_too_large. Shape the square yourself so the crop stays under your control.
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.
Why a Discord-oriented export often fails here
People reuse a Discord emoji file, or a README GIF cropped to a square, and expect Slack to take it.
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.
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.
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.
Crop, flatten, then thin the frames
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.
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.
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.
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.
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.
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.
A browser pipeline that follows that order
I built a Slack emoji maker 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.
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.
Names, and a last look before you upload
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 error_lower_case_names_only 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.
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.
These figures were checked on 17 November 2026. Check the current guidelines before you upload.
I build LoopGIF.
Top comments (0)