Skip to workspace
PixelOkay/ Video tools / Highlights Extractorđź”’ On-device editor
Tools
VIDEO CREATOR STUDIO

Video Highlights Extractor

Discover visually active moments, fine-tune every cut, and create a shareable compilation. No uploads, accounts or paid APIs.

Standard scanning uses scene and motion changes. Optional local vision AI can match described visual subjects, but neither method understands dialogue or subjective importance.

Source & preview

No video loaded
Import a video to start.

Highlight editor

Review each candidate, adjust in/out points, reorder, or add your own moments. The graph shows relative visual activity, not semantic importance.

Suggested highlights appear here after analysis. You can also add them manually.

How it works

01 · Import

Load your video locally. The file stays in your browser.

02 · Discover

Scan sampled frames for scene and motion variation. Preview and choose moments yourself.

03 · Refine

Adjust every clip’s start/end, ordering, and title, then export a WebM compilation or CSV list.

What is and isn’t supported

Great for action, sports, screen recordings, and visually changing footage. Dialogue significance, emotional moments, and audio peaks are not detected. The scan now explains scene-change and motion evidence, and you can keep your existing cuts when rescanning. WebM export can include the source soundtrack when audio capture is supported by the browser. For frame-accurate editing, soundtrack preservation, or MP4 output, use a dedicated video editor.

Using Video Highlights Extractor

Create an editable highlight reel from sampled visual activity or optional local image/text matching. Trim and reorder candidate clips, choose an aspect ratio and crop focus, then export a browser-recorded compilation or edit list.

  1. Load a video and scan for visual changes, or explicitly set up the optional CLIP model and enter short descriptions of the moments you want to find.
  2. Review each suggested range, set precise in/out times, reorder or add clips, and preview the final aspect ratio and static crop focus.
  3. Export a WebM compilation, CSV edit list or JSON project. Include source audio only when the browser’s recording support makes it available.

Example: For a product demo, ask the optional model to match “hands assembling the device” and “finished product close-up,” review each proposed frame, trim the clips and build a 9:16 reel under 45 seconds.

Limits and privacy: Source video is capped at 1 GiB and two hours; the editor supports up to 40 clips and 180 seconds of compiled output. Visual scores are relative suggestions, not editorial judgments. CLIP compares sampled still frames with your text and does not analyze dialogue; its runtime and weights download from external hosts after setup. Crop focus is static, and WebM capture/audio support varies by browser.

Frequently asked questions

What does the optional AI use to find moments?

The local CLIP model matches sampled video frames against short descriptions that you provide. It does not listen to dialogue or decide what is important, so review and edit every suggestion.

Does the tool automatically make a finished highlight reel?

No. Scanning creates candidate ranges. You choose the in/out points, order and crop, then start the compilation export or save an edit list.

Related tools

LOCAL AI SETUP

Set up AI on this device

First, a model needs to be loaded on your device

Visual scanning and WebM/CSV/JSON exports run without AI. Optional on-device CLIP vision AI scores sampled video frames against your scene descriptions. Loading a model requires an explicit click and may download hundreds of megabytes from public hosts. Scene text and locally sampled frames are processed on-device; model and runtime files download from public hosts after your approval.

  1. 1. Check device
  2. 2. Download / cache
  3. 3. Initialize model
  4. 4. Rank frames
CLIP zero-shot image/text matching via Transformers.js 3.8.1, quantized ONNX, CPU/WASM. Model download may be several hundred MB; exact live requirement is unknown.

Device & model resources

Measurements may be approximate
Device RAM / model memoryChecking device information…

Live system RAM, model RAM and GPU memory are not reliably exposed in browsers.

Browser website storageChecking storage…

Site-wide estimate; includes other PixelOkay tools and is not RAM.

ONE ACTION · ALL RECOGNIZED AI MODEL DOWNLOADS

Free AI model storage across PixelOkay

Read-only scan of recognized WebLLM and Transformers.js model caches from this entire website origin, including other PixelOkay tools. Unknown caches and browser databases are left untouched.

Run a scan to see how many model caches can be cleared together.

Browser-native models and unknown IndexedDB/OPFS or private runtime caches may remain. Unknown application/user storage will not be deleted. Other running tools might redownload caches; close their tabs first.

Having trouble downloading or loading AI?

Try refreshing device/storage, Retry Setup, or a different browser. Cache cleanup is optional and must be confirmed; it may require other AI tools to download models again. Never clear all website data without exporting your work.

Standard visual scanning and exports work without AI. The optional CLIP classifier runs on CPU/WebAssembly (WASM), not WebGPU, and needs enough device memory.
Recovery and technical details

If setup fails, review the stage and retry. A WASM CPU inference is supported in many browsers but can be slow.

Clearing all website data can permanently erase saved projects or drafts across PixelOkay. This tool never clears general site data.

CROSS-TOOL MODEL CACHE CLEANUP

Delete recognized AI model downloads?

Only verified model cache entries/buckets in this browser origin will be removed. Other PixelOkay tools may need to redownload those models. Unknown caches, IndexedDB, OPFS, projects and chats are not targeted. Close other AI tabs first.