When you use Loom’s “Stitch” tool to combine multiple recordings into a single presentation, video artifacts can appear at or near the seam where clips join together. These artifacts show up as momentary green screens, severe pixelation (macroblocking), screen tearing, dropped frames, or video that freezes while the audio continues playing. This corruption occurs when the stitched clips have mismatched resolutions, differing frame rates, or cutpoints that do not align with compressed video keyframes.
Fast Fix
Ensure all video clips share the exact same resolution and orientation (such as 1080p full-screen) before stitching them together. Avoid combining a vertical mobile recording or a scaled window capture with a full-desktop recording. After stitching, allow 10 to 15 minutes for Loom’s cloud servers to finish the high-definition re-encoding pass before viewing or sharing the video.
Diagnostic Snapshot
| Parameter | Operational Detail |
|---|---|
| Failure Layer | Cloud container concatenation, GOP (Group of Pictures) boundary misalignment |
| Artifact Types | Macroblocking, green screen flashes, frame jitter, audio-video desync |
| Common Trigger | Joining clips with different aspect ratios, resolutions, or variable frame rates |
| Recovery Path | Cloud re-render, resolution normalization, or raw clip export for local assembly |
Why Video Stitching Produces Artifacts
Loom encodes videos using compressed streaming formats (such as H.264/AVC). In these codecs, not every frame contains a complete image:
- I-Frames (Keyframes): Full, standalone pictures that contain complete visual data.
- P-Frames and B-Frames (Delta Frames): Partial frames that only store the pixels that changed since the preceding frame.
Clip A: [I-Frame] ──► [P-Frame] ──► [P-Frame] (Split Made Here)
│
▼ (Encoder Tries to Connect)
Clip B: (Cut Starts Here) ────────► [P-Frame] ──► [I-Frame]
│
▼
Result: Green Flash / Macroblock Corruption (Missing Reference Frame)
When you stitch Clip A to Clip B using Loom’s cloud editor, the rendering engine must reconcile two separate video containers:
- Broken Keyframe References: If the transition occurs on a delta frame rather than a clean I-frame, the decoder tries to render pixels using reference data that does not exist in the new clip, creating green flashes or pixelated squares.
- Dimension and Timebase Mismatches: If Clip A is recorded at 1920×1080 at 30 fps and Clip B is a browser window recorded at 1440×900 at 60 fps, the unified video container struggles to reconcile the differing dimensions and timestamps, causing screen tearing and audio drift.
- Premature Preview Inspection: Immediately after clicking “Save,” Loom displays a temporary low-bitrate stitched preview while the full-quality file compiles in the background.
Step-by-Step Resolution
Step 1: Wait for Cloud Re-encoding to Complete
Do not assume artifacts in the first few minutes after saving indicate a broken final video:
- Open your newly stitched video on Loom.com.
- Check the gear icon at the bottom right of the player:
- If you only see 720p or lower available, the server is still processing the high-definition stitched container.
- If the video is stuck rendering indefinitely, troubleshoot the queue using Fix: Loom “Processing” Loop (Video stuck at 0%).
- Wait 10 to 15 minutes, refresh the page, and check the seam again at 1080p. In many cases, cloud transcode passes clean up temporary macroblocking automatically.
Step 2: Normalize Resolutions Before Combining Clips
Never stitch clips recorded under different capture parameters:
- Match Display Scales: Avoid joining a full-screen desktop capture with a cropped window capture. If one of your clips was automatically recorded at a lower resolution due to display scaling, review Fix: Loom “Resolution Mismatch” (1080p recording showing as 720p) to match your recording settings before capturing replacement clips.
- Avoid Mobile and Desktop Hybrids: Do not stitch vertical recordings made on the Loom mobile app directly into horizontal desktop presentations.
Step 3: Add Buffer Room at Cutpoints
Tight cuts that trim right up to the exact millisecond someone speaks or moves often land on broken delta frames:
- Open the video in Loom’s editor and select Trim and stitch.
- Adjust your cut so there is at least one full second of stationary, quiet footage before the transition into the next clip.
- A brief stationary pause gives the H.264 video encoder a clean window to generate a fresh I-frame (keyframe), which prevents green frames and visual tearing at the seam.
- If you encounter issues while saving these cuts, follow the steps in Fix: Loom “Video Trimming” tool failing to save edits.
Tight Cut (Mid-Motion): [Fast Movement | CUT] ──► Pixelation and Glitches
Padded Cut (Stationary): [1 Second Still | CUT] ──► Clean Keyframe Generated
Step 4: Stabilize High Frame-Rate Source Clips
If one of your clips was recorded during a complex application demo with a variable frame rate, the stitcher will struggle to synchronize the combined audio and video tracks:
- If your demo recordings drop frames or stutter before stitching, resolve encoder strain using Troubleshooting: Loom “Frame Rate Drop” during Software Demos.
- Ensuring all source clips run at a consistent 30 or 60 fps prevents audio/video sync drift after stitching.
Fallback: Local Assembly for Mission-Critical Videos
If Loom’s web stitcher consistently introduces artifacts on high-resolution recordings, bypass the cloud editor:
- Download the original, unstitched clips directly from Loom.com.
- Import the
.mp4files into a dedicated video editor (such as QuickTime, DaVinci Resolve, or Adobe Premiere). - Export the combined file at a fixed 1080p resolution and re-upload the finished video directly to your Loom library.