WEBM is common for screen recordings made in a browser and for video saved from the web. Attach the WEBM to ToolGPT, say how small it needs to be, and the assistant plans a smaller copy that you approve before it runs.
Drag the recording into the chat, or pick it with the + button.
Name a size, a resolution or where the file is going. ToolGPT shows a plan with the estimated size, the format and codec, and the frame rate.
Press Start compression. When the job is done, the smaller WEBM shows up in the chat with a download button.
A WEBM file is compressed to WEBM by default. The video is encoded with VP9 and the sound with Opus, the codecs WEBM is built around. The plan shows this as "WEBM · VP9".
WEBM output is written by your browser's own video encoder. If your browser cannot encode WEBM, the job cannot finish in that format. In that case, ask for an MP4: ToolGPT can also write MP4 with its built-in FFmpeg when the browser cannot.
A recording of slides, code or a document changes little from one frame to the next. That is why it can often go to a much lower bitrate, or a lower frame rate, and still be easy to read.
Tell ToolGPT what the recording shows, and it can suggest a lower frame rate or resolution along with the bitrate. If the recording is already compressed so well that the plan would not make it at least 5% smaller, ToolGPT tells you instead of making a bigger file.
WEBM plays in modern browsers and many video players, but some phones, editors and email previews handle MP4 more reliably. If the person receiving the file may not open WEBM, ask ToolGPT to compress it as an MP4 with H.264 video. The compression runs in your browser either way.
Yes. That is the default for a WEBM file, as long as your browser can encode WEBM.
Yes. The audio is kept and encoded as Opus.
No. It is compressed in your browser. The assistant only receives details such as the file's name, length and resolution.
Try it with your own file
Open ToolGPT, attach a file, and type what you want done.