2026-10-06
GIPHY Clips cap at 30 seconds and 100MB — its free GIF Maker states no length limit at all (GIPHY’s own pages)
"Upload a video to GIPHY" sounds like one destination with one spec sheet. It's actually two — and they don't share a size limit, a duration limit, or even who's allowed to use them. GIPHY Clips are, in GIPHY's own words, "GIFs with Sound" — real video with audio, not a silent looping image — and GIPHY's own support article on them states plainly that creating one isn't open to everyone. The plain GIF Maker at giphy.com/create is the one everybody can use, takes video in and a silent GIF out, and states no duration limit on its own page at all — which doesn't match the specific second counts ("6 seconds," "15 seconds") that several unrelated guides repeat as if GIPHY itself said so.
GIPHY Clips: real numbers, and a real gate most people hit first
GIPHY's own Clips Best Practices support article is specific where the GIF Maker page isn't: a Clip runs up to 30 seconds, up to 100MB, as an MP4, MOV, or WebM file, between a 9:16 and a 16:9 aspect ratio, at up to 4K resolution and 24 or 30 frames per second. Those numbers would make a reasonable target to trim and convert toward — except the same article states the part that matters more for most people reading this: "Clips creation is only available for upgraded Brands and Artists." Watching and sharing an existing Clip is open to anyone; making a new one, with your own footage, isn't — it requires applying for an upgraded channel first. If that's not your account, the 30-second/100MB spec above is a path you don't currently have, not a bug in anything NearVid does.
The GIF Maker almost everyone actually uses
The page everyone without an upgraded channel lands on instead — giphy.com/create/gifmaker — accepts "JPG, PNG, GIF, MP4, MOV, or WebM" going in, per its own interface, and converts a video into a silent, looping GIF. That page does not state a duration limit anywhere in its own text. The specific second counts that circulate as "the GIPHY limit" come from unrelated guides, not from this page or any other GIPHY page found in this research — they're left out here rather than repeated as fact. The one number that is official and documented comes from a different page entirely: GIPHY's own Upload API documentation states "We accept animated GIFs or video files up to 100MB" — the same ceiling Clips use, on the upload side, even though the GIF Maker's own page doesn't repeat that number itself.
Where NearVid's existing 10-second GIF cap actually comes from
NearVid's GIF export has always capped the source range at 10 seconds — not a number picked to
match GIPHY, but one already in the product: workspace.js hardcodes it as
const cap = 10, sourced in its own comment to the product's "<=10s recommended"
guidance, enforced rather than left as a suggestion. That happens to land comfortably under every
length figure GIPHY actually states anywhere — the 30-second Clips ceiling, and the complete absence
of a stated duration on the GIF Maker's own page. It isn't a coincidence built for this post; it's
the same cap that was already there before this research started, confirmed directly against the
source rather than assumed.
No size estimate for GIF — on purpose, not an oversight
NearVid shows a live "≈" expected-output-size estimate next to the quality selector for its WebM
and Convert-to-MP4 operations, calculated from a fixed bitrate preset times duration (confirmed in
workspace.js's updateQualityEstimate()). That function returns early and
shows nothing for the GIF operation — state.op !== 'webm' && state.op !== 'mp4' clears
the field rather than filling it with a guess. A GIF has no fixed bitrate the way an encoded video
does: the same 10 seconds at the same width and frame rate can come out wildly different sizes
depending on how much the footage's colors and motion actually change frame to frame, which a
bitrate-times-duration formula can't account for. Leaving the field blank for GIF, rather than
showing a number that would often be wrong, is the same "honest unknown" NearVid already practices
for an unprobed file's duration — just applied to one more field.
If you do have Clips access: trim and convert, not GIF-export
A Clip keeps its audio, which means the GIF export path — which never touches an audio track — isn't the one to use. NearVid's lossless Trim cuts to an exact in/out point without re-encoding, and its Convert to WebM or Convert to MP4 (H.264+AAC via WebCodecs/Mediabunny, gated on browser support) produce one of the three formats GIPHY's own article lists for Clips. Neither operation resamples frame rate or resizes the frame — if your source footage isn't already 24 or 30fps, or isn't already between 9:16 and 16:9, that's true of it before NearVid touches it, and still true after. What NearVid does handle mechanically is landing the clip at or under 30 seconds and in an accepted container, on-device, without the footage — audio included — leaving the browser tab to do it.
What this doesn't do
NearVid doesn't upload to GIPHY, doesn't check or apply for an upgraded Brands/Artists channel, doesn't crop or resize a frame into GIPHY's aspect-ratio range, and doesn't optimize a GIF's color palette or frame count the way a dedicated GIF tool might. What it does do is the two things that are purely mechanical either way: cutting to the right length without re-encoding, and — for a Clip, specifically — producing an accepted container with the audio intact, on whichever device the original footage is already on.
The honest summary
GIPHY Clips and GIPHY's plain GIF Maker are two different tools with two different spec sheets, not one feature with one limit: Clips cap at 30 seconds and 100MB but require an upgraded Brands/Artists channel to create at all, while the GIF Maker anyone can use states no duration limit on its own page, sitting only under the same 100MB upload ceiling GIPHY's API documentation states separately. NearVid's GIF export was already capped at 10 seconds before this research started, comfortably under both figures, and deliberately shows no size estimate for GIF exports rather than guess at one. For a Clip specifically — audio and all — Trim plus Convert to MP4 or WebM gets the length and container right; the aspect ratio and frame rate are still the source footage's to arrive with.