Remote work produces two kinds of file work: explaining something on screen, and moving a document between people. The first is a recording chain. The second is a merge, sign and encrypt chain. Both are short, and both fail at the last step when the order is wrong.
Record, convert, then compress, because compressing a WebM and converting it afterwards re-encodes twice. For documents, merge before signing and sign before encrypting, because a signature has to sit on the final page count and an encrypted file cannot be edited without unlocking it. Every step except speech recognition runs in the browser.
1. Record the walkthrough
Screen Recorder captures a whole screen, a window or a single browser tab, with optional microphone audio mixed into the recording. The output is WebM with VP9, with no watermark and no hard time limit. The page must be opened over HTTPS, and the browser asks for screen and microphone access before anything starts.
Keep sessions under about thirty minutes, because the recording is held in browser memory, and use pause between sections rather than one long take. One limit matters for meetings: the tool promises microphone audio, not system audio, so it records your voice rather than the sound coming out of your speakers. For a demo, a code walkthrough or a bug report that is exactly right. For capturing a call with other people, use the meeting software's own recorder.
Screen Recorder
Record a screen, window or tab with optional microphone audio, no watermark.
2. Convert, then compress
WebM plays in Chrome, Edge and Firefox, but not everywhere. Video Converter rewrites it to MP4 with H.264, which is the safest format when the recipient opens the file in an unknown player. If the recording came from somewhere else as MOV or MKV, the converter handles those too.
Video Compressor sets output format, quality, resolution and frame rate. Dropping 1080p to 720p and lowering the frame rate is usually enough for a chat app without making on-screen text unreadable. Clips under 200 MB and a few minutes long are the comfortable range because every frame is processed locally, and the first run downloads the FFmpeg engine of about 30 MB. There is no target size field, so you lower the settings and check the result.
Video Compressor
Bring a walkthrough down to a shareable size with format, quality and resolution controls.
3. Transcribe, with a privacy caveat
Video to Subtitles turns a recording into a transcript with timecodes and can label speakers, which is useful for an interview or a review call. You can edit names, numbers and wording in the preview before saving, and download SRT, VTT or plain text. A free run covers 2 minutes of media per day, a free account receives 5 credits a day, and the upload limit is 30 MB.
This is the one step that is not local. The file is uploaded to a server and forwarded to Volcengine AI MediaKit, so do not put a confidential meeting through it. The recogniser also supports Simplified Chinese and English only. If the video stays internal and only needs captions for viewers, Add Subtitles can burn a prepared SRT into the file locally, though its renderer covers Latin scripts only.
Video to Subtitles
Transcript with timecodes and speaker labels. Uploads the file and uses Cloud AI credits.
4. Merge, sign and encrypt the document
The order is fixed by what each step does. Merge PDF joins the cover note, the contract and the appendix into one file, so the signature lands on the final page count. Sign PDF then places a drawn or uploaded signature image on the page, in one of nine positions with a 5 percent page margin. Protect PDF goes last and writes AES-256 with printing, copying and editing permissions.
The reason for that order is practical. Once a PDF is encrypted, every other tool has to decrypt it, so signing or numbering afterwards means unlocking, editing and protecting again. And any rewrite invalidates a cryptographic signature, so a signed original stays untouched and a separate copy is compressed or watermarked if needed.
Two limits to state plainly. The signature here is an image, not a qualified electronic signature: no certificate, no audit trail, no timestamp. And Protect PDF has no password recovery, so a lost password loses the file for everyone, including you.
Protect PDF
Add AES-256 encryption and printing, copying and editing permissions, locally.
What this workflow cannot do
- It is not a meeting recorder. Screen Recorder captures the screen and your microphone, not system audio, so it cannot record the other side of a call.
- It is not a video editor. There is no timeline, no cutting and no joining. Those live in Video Trimmer and Video Merger as separate passes.
- Transcription uploads the file. Video to Subtitles sends the recording to a server, caps uploads at 30 MB, and recognises Chinese and English only.
- Burned-in captions are Latin-only. The subtitle renderer bundles a single Latin font, so other scripts may show as empty boxes.
- No qualified e-signature. A drawn or uploaded signature has no certificate, timestamp or audit trail.
- No target file size. Compression reports what it achieved; it cannot promise a chat app's exact limit.
- No integrations. Nothing connects to Slack, Drive, Notion or a ticketing system. You download the file and upload it yourself.