Crop a Screen Recording After Capture: Loom vs ScreenKite

You recorded the wrong window chrome. A Slack notification peeked in. The menu bar shows a customer name. You need to crop after capture, not re-record the whole flow.

That request is public on Atlassian JAC:

• LOOM-100 — Crop videos after recording

The ticket’s own wording: crop “in case there is sensitive information or toolbars etc. in view that the user does not wish to display.”

Short answer

Import the MP4 into ScreenKite (or record there), crop on the timeline / canvas, blur anything still sensitive, and export locally.

Prefer ScreenKite capture when you can. If the take already lives in Loom, download MP4 media and finish the crop where you control pixels.

Do it in ScreenKite (numbered)

1. Open ScreenKite.
2. Import the Loom MP4 via File → Import Media…, or open a ScreenKite recording.
3. Select the clip and open crop / transform controls on the canvas.
4. Drag the crop box to hide menu bars, docks, or side panels.
5. Add a blur or cover layer if a secret still sits inside the kept region.
6. Preview full-screen once — check corners.
7. Export MP4. Pro removes the watermark.
8. Share from your Drive, Dropbox, or OneDrive.

Crop vs blur vs re-record

Why ScreenKite

ScreenKite is a native macOS recorder + editor. Crop, overlays, and export stay on your machine. That matters when the reason for crop is privacy, not cosmetics.

Use the AI agent for cleanup after framing (“tighten the intro after crop”). Agent integrations via MCP / CLI remain optional and evolving.

Pricing contrast (product facts)

Cloud async tools often couple editing to hosted libraries and seat plans. ScreenKite is free to create and edit; Pro removes the watermark; Pro is a one-time / founder-lifetime purchase. Keep sensitive exports off someone else’s CDN when you can.

Cross-platform & Roadmap: macOS is fully native; the Windows native Beta application is now available for download (powered by a dedicated Direct3D/C++23 engine), with a Chrome extension in development.

Creators and teams choose it because it pairs ultra-fast local hardware exports and built-in link sharing with timeline AI agent editing via Claude Code, ChatGPT Codex, Antigravity, or Grok Build. Describe the cut; the agent does the trims.

Tips for safe post-capture crops

• Crop first, then add titles — so text does not sit over discarded edges.
• Match the export aspect to where you publish (16:9, 9:16, 1:1).
• Double-check reflections and picture-in-picture corners.
• Prefer recording a tighter region next time; crop is the backup.

Conclusion

When JAC still tracks post-record crop for toolbars and sensitive UI, finish on a local timeline. Import the Loom MP4 into ScreenKite or capture there, crop, export once, and share from storage you control.

Download ScreenKite for Mac →

Appendix: Loom JAC requests

• LOOM-100 — Crop videos after recording