{# Als einziges Symbol OHNE fill-Attribut: Der Stern zeigt seinen Zustand ueber die Flaeche (.sts-star[aria-pressed="true"] svg { fill: currentColor }). Ein fill am symbol waere ein Praesentationsattribut und schluege die geerbte CSS-Angabe - der gemerkte Stern bliebe dann eine Kontur. #} {# Bedienungssymbole des Notizblocks. Quelle: Lucide (ISC-Lizenz), wie in der Design-Uebergabe "Alltagswerkzeuge v2". Geometrisch statt handgezeichnet: sie stehen in Leisten neben Text, nicht als Kategoriezeichen. #}
Small Things Sorted

Shrink a video

Under the attachment limit - with a target size instead of a guess.

Stays on your device – The video is processed in your browser. It is not uploaded.

The first click loads about 10 MB of processing module. Shrinking recalculates the picture and takes roughly as long as the video runs - longer at 1080p.

Drop your files here

or

You can also paste with Ctrl+V.

What you type is processed in your browser and never sent to us.

How to do it

  1. Pick your video

    Drop the file in or choose it.

  2. Choose a resolution

    720p is enough for almost anything sent by mail.

  3. State a target size

    Or use one of the two buttons.

  4. Go

    Afterwards it says what percentage of the original it became.

What this is for

The mail server takes 20 megabytes, the video is 180. The usual answer is a slider marked "quality" and three attempts.

Here you state the target size. The size and the length give the data rate needed - that is arithmetic, not a guess. For the two common cases there are buttons: 20 MB for e-mail, 15 MB for messengers.

There is a floor, and the tool names it. An hour of video in 20 megabytes would mean a data rate at which the picture breaks into blocks. Rather than hand over mush, the tool says beforehand that it will not work and suggests trimming the video or lowering the resolution.

Resolution is the second lever and the more effective one: from 1080p to 720p the pixel count nearly quarters, and the computing time falls with it.

Common questions

No. The processing runs in your browser.

Close, but not to the byte. The data rate is worked out from size and length and deliberately set a little under the target, because the container adds a few percent. After the run the actual size is shown, and whether your limit is met.

Because below about 150 kbit/s moving pictures break into blocks at any resolution. If your size divided by the length falls under that, it cannot be reached - then only a shorter video or a lower resolution helps. Handing over an unusable file would be the worse answer.

With heavy shrinking, the resolution. A 1080p picture with too little data looks worse than the same picture at 720p with the same data - fewer pixels, more data per pixel. That is why 720p is preselected here.

Roughly as long as the video runs. A smaller target resolution makes it quicker, because there are fewer pixels to compute. An estimate is shown before you click, the remaining time while it runs.

Missing a tool? Tell us which one.