Fix: Loom “Video Trimming” tool failing to save edits

When Loom’s “Video Trimming” tool fails to save edits, clicking “Save changes” or “Publish changes” results in an infinite loading spinner, a generic “Something went wrong” alert, or a silent revert back to the unedited source video. This failure occurs when the underlying video is still undergoing cloud transcoding, when stacking too many edit cuts creates an unstable render manifest, or when browser extensions intercept Loom’s timeline API requests.

Fast Fix

Save your trims one cut at a time instead of making multiple splits at once, and confirm the video has finished its high-definition cloud processing before editing. If saving still hangs, duplicate the video from the options menu and edit the clean duplicate in an Incognito window with ad-blockers and privacy extensions disabled.

---

Diagnostic Snapshot

Parameter	Operational Detail
Failure Layer	Web-based non-linear editor (NLE) API or cloud transcode lock
Common Symptoms	Spinner stuck on “Saving edits…”, error code 409/500, lost cutpoints
Affected Environments	Browser video editor (Chrome, Edge, Safari, Brave)
Admin Access Required	No (creator permissions on the video are sufficient)
Data Loss Risk	Low (original raw recording is preserved via non-destructive editing)

---

Why Video Trims Fail to Save

Loom uses non-destructive editing. When you drag a trim handle or delete a section, the editor does not immediately re-encode the entire video file on your computer. Instead, it generates a timeline manifest containing start and stop timestamps (e.g., keep: 00:00-01:15, cut: 01:15-02:10, keep: 02:10-05:00) and sends this JSON payload to Loom’s rendering servers via a PATCH request.

[User Applies Cutpoints in Browser]
                 │
                 ▼
[Generates Timestamp Manifest JSON]
                 │
                 ▼
     (API Request: PATCH /edits)
                 │
       ┌─────────┴─────────┐
       ▼                   ▼
[Video Still Transcoding]  [Browser Extension Block]
       │                   │
  HTTP 409 Conflict   Network Request Dropped
       │                   │
  Save Fails/Reverts  Infinite Loading Spinner

This workflow breaks under three specific conditions:

1. Asynchronous Transcode Conflict: If you record a 1080p video and attempt to trim it immediately after upload, the file is still actively being processed by Loom’s high-definition transcode engine. The server locks the video manifest to prevent file corruption, returning an API conflict error.
2. Manifest Payload Overload: When users attempt to make dozens of micro-cuts (such as trimming out every breath or filler word manually), the edit payload can exceed the timeout threshold for the web editor’s API call.
3. Ad-Blocker Interference: Extensions that block tracking or modify web requests can misinterpret Loom’s background editing pings as telemetry and block them mid-save.

---

Step-by-Step Resolution

Step 1: Confirm Background Cloud Processing Is Complete

Never attempt to trim a video that is actively transcoding:

1. Open the video page on Loom.com.
2. Check the bottom of the player and the settings gear:
   • If you see a notification stating “Processing higher quality…”, do not trim the video yet.
   • If your video is completely stuck and cannot finish its primary transcode, resolve that issue first by checking Fix: Loom “Processing” Loop (Video stuck at 0%).
3. Wait until the gear icon shows the full source resolution (1080p or 4K) before launching the trim tool.

Step 2: Make and Save Trims Incrementally

Stacking twenty cuts across a long timeline before clicking save dramatically increases the risk of a save failure:

1. Open the Edit menu and select Trim and stitch.
2. Make your primary opening cut (e.g., trimming off the first 5 seconds).
3. Click Save changes (or Publish changes) immediately.
4. Allow the system to confirm the single edit.
5. Re-open the trim tool to make subsequent cuts. Saving incrementally guarantees that you do not lose progress if an individual API call drops.

Step 3: Duplicate the Video to Clear Corrupt Edit States

If a video’s timeline manifest becomes corrupted from previous interrupted edits, it will reject all subsequent modifications:

1. On the video page, click the three dots (…) above the video.
2. Select Duplicate.
3. Open the newly created duplicate video.
4. Apply your desired cuts to the fresh copy. Duplicating generates a clean video container with a blank edit history, bypassing any corrupted manifest entries.

Step 4: Isolate Browser Extensions and Network Blocks

Browser security add-ons often block the WebSocket or API endpoints required to commit edits:

1. Open an Incognito / Private window in Google Chrome.
2. Log into Loom and navigate to your video.
3. Try saving the trim again.
4. If it works in Incognito, disable third-party extensions—particularly privacy shields, ad-blockers, and third-party script filters.
5. If you are combining multiple clips together and encountering playback glitches alongside trim failures, see Fix: Loom “Stitch” tool causing Video Artifacts.

Step 5: Check Cloud Sync and Media Offline Warnings

If your local browser session lost sync with Loom’s storage bucket while the editor tab remained open, the editor cannot commit the cut points. Verify that your video is fully online and accessible across devices by reviewing Fix: Loom “Cloud Sync” delay causing “Media Offline” in Browser.