There was an error while loading. Please reload this page.
Updated Animated GIF and WebP Size Capacity (markdown)
Split capacity guidance by output format and soften to approximations Profiling identical content as both formats showed GIF costs up to 1.78x WebP at larger output sizes, so a single frame-count table cannot serve both. Adds separate GIF and WebP tables, recalibrated against four measured animations rather than one. Also states plainly that these are approximations with ~25% run-to-run variance rather than thresholds, adds converting GIF to WebP as the least destructive remedy, and restores the note that the largest displayed size affects available headroom. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Revise animation capacity guidance from live measurements Frame budgets are now set by the 30-second processing limit rather than Sharp's 268M pixel ceiling, which testing showed is reached roughly three times later than the time budget. Also distinguishes the two failure modes: an oversized animation that Sharp refuses outright (original served unscaled) versus one that starts resizing and cannot finish (request fails, nothing cached), and documents that a failed first load resolves itself once the scaled version is saved. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Updated Animated GIF and WebP Size Limits (markdown)