360×360, 650KB, 24 Frames: the Three Numbers That Decide Your Emoticon’s Fate

A Kakao animated emoticon is a set of up to 24 WebP files at 360×360 pixels, each capped at 650KB and 24 frames, that loops exactly 4 times inside the KakaoTalk chat interface.

The ceiling most creators never hit — and the floors that actually reject them

The 650KB cap on Kakao animated emoticons is real. It is also, in practice, rarely the number that kills a submission. Our own measured files — a 24-frame animation at 360×360 came in at 146,290 bytes on a successful live submission, and a separate 18-frame test file measured 116,432 bytes — sit so far below the ceiling that the cap itself was never in play.

The pattern the spec creates is this: 650KB is the ceiling, but loop count, frame count, and toolchain rules are the floors most submissions trip over first. A file can be small and still fail every other gate.

What the spec actually requires (all four must pass simultaneously)

Kakao Emoticon Studio’s published specification, as read directly from kakaoemoticonstudio.notion.site, sets the following hard limits for animated emoticons:

A 24-image set allows the remaining 21 files to be static PNG. But the 3 animated WebP files are mandatory at submission — missing them means the set cannot be reviewed at all.

The loop count deserves emphasis. Four loops is not a minimum; it is the exact value. An animation that loops 3 times or loops continuously does not match the spec. This is a binary pass/fail with no partial credit.

Why the toolchain rule matters more than you think

The spec adds a constraint that sits outside any single file: WebP files must be produced using Kakao’s own dedicated WebP Animator tool. The upload interface accepts image/png and image/webp, so a file from a third-party encoder will pass the file-type check. It will not necessarily pass review.

This is where creators using general-purpose animation exporters — After Effects, ScreenToGif, FFmpeg pipelines — face a hidden trap. The file looks correct by every number. The toolchain is wrong.

Our live successful submission used the specified workflow: 360×360, 24 frames, 146,290 bytes, produced through the designated path. The measured result cleared every gate. The file size used roughly 22% of the 650KB budget.

The gap between “it works once” and “it works consistently”

A submission that passes format checks still faces review. The format gate is necessary but not sufficient. What the spec constraints define is the boundary of what can be reviewed — not what will be approved.

IBM Research published findings on September 15, 2026 that are structurally relevant here: on AppWorld, a ReAct agent using GPT-4.1 succeeded on 77.4% of runs on average, but succeeded on all five repetitions for only 53.0% of tasks — a 24.4-point consistency gap. The point applies to any multi-step submission process: average pass rate and consistent pass rate are different numbers, and the second one is what production reliability actually means.

For emoticon creators, the translation is direct. A set that clears format review once is not guaranteed to clear it again if any parameter drifts — frame count creeps up during revision, a file gets re-exported through the wrong tool, a loop value changes. Repeatability requires locking every parameter, not just checking it once.

The decision rule for creators

Three questions sort whether a rejection is recoverable in the current submission cycle or requires a full rebuild:

Does the file exceed any hard number? Check canvas (360×360), size (≤650KB), frames (≤24), and loop count (exactly 4) before anything else. These are binary.

Were all files produced with the designated WebP Animator? If any file came from a different encoder, re-export before resubmitting. The format check passes; the toolchain check does not.

Does the set include at least 3 animated WebP files? A set of 24 PNGs with 2 animations cannot be submitted. Swap a third static file for an animation before the submission attempt.

Creators who build a validation checklist from the published spec — and run it before each export, not only before submission — eliminate the rework cycle that format rejections create. The 650KB ceiling is generous. The frame, loop, and toolchain constraints are not.

Looking for more on ai & digital income? Visit SAVYX

Frequently Asked Questions

What is the exact file size limit for a Kakao animated emoticon?

The published spec caps each animated WebP file at 650KB. In practice, well-optimized 24-frame animations at 360×360 pixels typically land well below this ceiling — our measured live submission came in at around 146KB — so frame count, loop count, and toolchain compliance are more commonly the constraints that require attention.

How many times must a Kakao animated emoticon loop?

Exactly 4 times, according to the Kakao Emoticon Studio specification. This is not a minimum; it is the required value. An animation set to loop continuously or to stop at 3 repetitions does not meet the spec.

Can I use After Effects or another tool to export my animated WebP files?

The published spec states that WebP files must be created using Kakao’s own dedicated WebP Animator tool. A file exported from a third-party encoder may pass the file-type check at upload but can fail at review stage. Re-export through the specified tool before submitting.

Do all 24 emoticon files need to be animated WebP?

No. The spec requires a minimum of 3 animated WebP files in the submission set; the remaining files (up to 21 in a 24-image set) may be static PNG. However, the 3 animated WebP files are mandatory — the set cannot proceed to review without them.

What frame count is allowed for Kakao animated emoticons?

The spec sets a maximum of 24 frames per animated WebP file. There is no published minimum, but the loop count requirement of exactly 4 repetitions means very low frame counts will produce very short animations. The successful measured submission used 24 frames at 360×360 pixels.

Disclosure: As an affiliate, this post may earn a commission from qualifying purchases at no extra cost to you.