How we test, and what to expect

Current technical limits

Reviewed 10 October 2026. These limits come from the same configuration used by the processing modules. MiB and GiB are binary units; older interface labels abbreviate them as MB and GB. Limits are safety caps, not guarantees that every device can complete the largest job.

Limits by processing workflow
WorkflowEnforced limit
Frames / JPG / PNG / endpoints2 GiB source; 8,294,400 decoded pixels; 120 pictures or 96 MiB gallery
Contact sheetsSame source limit; 120 samples; 16,000,000 output pixels; 8192 pixels per side; 1–8 columns
Video conversion / audio / captions100 MiB source; 600 second selected range
Fast 2× video enlargementSame media limit; 8,294,400 output pixels (source pixels × 4)
Optional AI videoSame media file size; 320 × 180 source; 10 second range
Portrait removal / English OCR20 MiB source; 4,000,000 source pixels
Image enlargement50 MiB source; 16,000,000 source pixels; 8192 source pixels per side; 2× dimensions (up to 64,000,000 output pixels)
Image Resizer50 MiB source; 16,000,000 source/output pixels; 8192 pixels per side
Canvas animation preview2–60 images; 24 MiB total; 16,000,000 pixels per input; 640 × 360 preview
Frame calculatorsEntered FPS above 0 through 240; result up to 1,000,000,000 frames

Frame capture admits by total pixels, not one fixed landscape shape: 1080 × 1920 portrait fits, while 4096 × 2160 exceeds 8,294,400 pixels. There is no universal decoder or 8K capture. AI image enlargement can require several large buffers; a 64-MP output is particularly demanding on mobile.

Image Fast resize needs no model. Optional Auto switches to AI at 524,288 source pixels or below. AI video is independently sampled enhancement, not interpolation. Capturing every source frame and exact variable-frame-rate indexing are not implemented.

These tools are designed to create useful files while making their limits visible. A successful test means the described operation produced an inspectable output for the specified input. It does not establish that every file, device, or AI prediction will work equally well.

What was checked in this release

On 3 October 2026, the local Chromium-based in-app browser completed 17 feature checks and 12 edge-case checks. The saved files were also inspected independently. The test fixtures used generated video patterns, known stereo tones, printed English text, a synthetic portrait, and the official Whisper speech-test recording.

OperationObserved result
Frame extraction and ZIPFour timestamped PNG files; a real ZIP passed its CRC checks.
Audio extractionMP3, WAV, M4A, and OGG outputs. The WAV duration was 3 seconds; a trimmed WAV was 1 second.
SubtitlesReviewed SRT exported; visible caption text was confirmed in a decoded MP4 frame. English speech produced timestamped draft captions.
AI image enlargementA 128 × 96 sample produced a 256 × 192 PNG.
AI video enlargementA short 160 × 90 sample produced a decoded 320 × 180 frame.
Portrait backgroundA 256 × 256 sample produced an RGBA PNG with both transparent and opaque pixels.
OCRThe known printed English sample text was recovered.

Expanded image and workflow checks

The revised image upscaler passed 11 additional checks, including large PNG/JPG/WebP and SVG images, portrait input, tiled AI, transparent output, invalid-file recovery, cancellation, and a 4000 × 4000 source producing an 8000 × 8000 PNG with Fast resize. Auto clearly identifies whether AI enhancement or ordinary resizing was used.

All 16 frame-workflow pages produced real 160 × 90 sample captures with the expected defaults and no measured mobile overflow. An additional test captured a compatible H.264/AAC MKV fixture. These checks cover controlled examples, rather than every codec or recording device. The shared 12 edge checks were rerun after the image changes.

Errors and cancellation matter too

The browser checks included missing inputs, reversed time ranges, malformed subtitles, invalid image bytes, oversized images, mono audio rejection for centre cancellation, repeat conversions, and cancellation/recovery. OCR was cancelled during recognition and then successfully run again.

What has not been established

These results do not establish broad Safari, Firefox, Android, or iPhone compatibility, professional restoration quality, or perfect transcription. Models can hallucinate detail or words. Browser playback is codec-dependent. Keep the original, compare the output, and use a short test before committing to a workflow.

Live hosting redirects, model delivery, contact mail delivery, search indexing, and account approvals must be checked after deployment. A local test cannot establish those external outcomes.

Choose a tool or report a reproducible problem. Include the tool, browser, format, and error message; please do not send private media.

Inspect the actual sample exports

These files came from the recorded local-browser tests. The frame source is the generated demonstration video available through “Try sample video” in the extractor. For the sequence test, the selected range was 0–2 seconds, the interval was 0.5 second, and PNG was selected. The end is excluded, giving four timestamped files at 0, 0.5, 1 and 1.5 seconds. Each decoded image is 1280 × 720; this is an HD demonstration, not a 4K compatibility test.

Actual extracted demo frame showing a purple moving circle and a zero-second timestamp
First PNG from the generated demo. The downloaded file has the source frame dimensions.

Download the four-frame test ZIPRepeat the extraction test

Open the archive and check the filenames, image dimensions and changing timestamps. A CRC check passed for this saved archive. A successful sample demonstrates this workflow; it does not establish that an arbitrary MOV, HEVC recording or HDR video will produce the same result.

Compare a small AI enlargement

The original generated 128 × 96 image and the actual 256 × 192 ESRGAN output are both available below. Inspect them at their actual dimensions and compare edges and small details. A larger image is an inferred result, not proof that detail existed in the source.

Original 128 by 96 generated test image with a circle and diagonal line
Original · 128 × 96
Actual 256 by 192 ESRGAN output of the generated circle and line image
AI output · 256 × 192

Download the original PNG · Download the actual enlarged PNG · Try the image upscaler

Canvas sequence prototype checks

The canvas guide was checked with PNG, JPG and WebP inputs, numerical filename ordering, first and last frames, optional scrolling, corrupt-file recovery, clearing during decoding and reduced-motion preferences. The downloaded HTML example reopened locally and displayed all 30 generated sample frames. Its embedded images are resized previews at 640 × 360, not replacements for the original exports.

Use the canvas sequence guide to repeat those steps. These are dated local checks from 3 October 2026; they do not establish a browser-wide compatibility certification or an account approval.

Fast browser processing and compatibility

Image resizing uses canvas without an AI model. Fast image and video enlargement resize existing pixels; they do not restore missing detail. Supported browser codecs are tried first for video compression and audio extraction. Native stereo audio processing avoids the media engine when decoding is supported. Unsupported codecs use FFmpeg; background removal, OCR, automatic transcription and optional AI enlargement still need engine or model files. Downloads can be cached, but cleared storage, a new device or private browsing may require them again. Encoding speed and AI quality vary by device and source. No workflow is guaranteed instant.

The Image Resizer accepts supported images up to 50 MB and 16 MP, with output up to 16 MP and 8192 pixels per side. Animated images export one still frame. Exact dimensions refer to the canvas; Fit may add padding and Fill crops the centre. Fast video enlargement allows output up to 8.3 MP. Optional AI video retains the 320 × 180 source and 10-second limits.