UncrushView build status

In development

Will the platform
crush your video?

Uncrush is building a safer, evidence-driven way to prepare creator videos for upload without blindly re-encoding them or changing their artistic intent.

Explore the technologySee what exists today
01

The problem

You made the image.
The platform makes another.

Creators spend time on lenses, light, color, cadence, sound, and export. Upload platforms still generate their own delivery renditions for viewers.

One project hypothesis is that an enormous source file may not produce a proportionally larger delivered bitrate. Controlled rendition tests are needed before that can become product guidance. Creator advice is still crowded with magic settings and copied thresholds.

02

The approach

A proof chain,
not a preset.

Four deliberate stages keep preparation separate from platform claims.

  1. 01

    Inspect

    Read the supported container structure, encoded tracks, decoder setup, and exact timing under explicit limits.

  2. 02

    Prepare

    Plan narrow container changes around the source instead of reaching first for another encode.

  3. 03

    Verify

    Reopen the generated file and compare the encoded media and required meaning before it can be published.

  4. 04

    Measure

    Test real delivery renditions under controlled conditions before turning a hypothesis into product guidance.

03

Preservation

Engineering priority

Keep the decisions already in the footage.

Quality means more than pixels. Timing, cadence, motion, color, audio, and decoder setup all shape the result.

  • 01Encoded samples
  • 02Real sample order
  • 03Exact timing
  • 04Source cadence
  • 05Natural motion blur
  • 06Color meaning
  • 07Audio meaning
  • 08Decoder configuration

Verified now

Read-only comparison

The current foundation directly verifies encoded samples and supported container semantics between two files.

Implemented now

Verified fast-start

The native CLI creates verified same-container fast-start copies through source-bound planning, bounded streaming output, independent re-analysis, and mandatory safe-transform-v1 publication gating.

04

Local-first

Planned browser direction

The future processor is designed to work where your footage already is.

A future browser processor is designed to run approved media preparation locally. No file processing exists on this site today.

05

Current status

Built in layers.
Claimed with care.

Read the full status matrix

Current code · v0.1

Implemented

The native codebase analyzes supported MOV/MP4, verifies encoded media and container semantics, creates same-container fast-start copies, and remuxes one closed QuickTime profile to verified MP4.

  • Bounded MOV/MP4 analysis
  • Canonical encoded-sample identity
  • Direct safe-transform-v1 verification
  • Native CLI foundation
  • Source-bound transformation planning
  • Bounded streaming container writer
  • Verified faststart-v1
  • Generated-output re-analysis
  • Verified MOV-to-MP4 remux
  • Mandatory publication gate

Current boundary

In development

No browser processor or next media transformation is active. Uncrush will define the next phase in a separate design.

    Later milestones

    Planned

    Browser/WASM processing, platform profiles, and controlled platform research require separate milestones and evidence.

    • Browser WASM processor
    • Versioned platform profiles
    • Controlled rendition experiments
    • Mobile applications

    Evidence boundary

    Not claimed

    Uncrush publishes platform-quality statements only after controlled, reproducible testing supports them.

    • No public processor yet
    • No proven TikTok-quality result
    • No upload automation
    • No decoded-media claim
    06

    FAQ

    Straight answers,
    before launch.

    Does Uncrush upload my videos?

    No. This website has no video input, upload service, account, or processor. A future browser processor is intended to prepare supported files locally.

    Does it convert 25 fps to 60 fps?

    No. The normal preservation path is designed to keep source cadence. It will not invent frames or turn 25 fps footage into 50 or 60 fps.

    Does it remove natural motion blur?

    No. Motion blur created by the camera and shutter choice is part of the footage’s artistic intent. Uncrush is designed to preserve it.

    Does it guarantee better TikTok quality?

    No. Uncrush has not produced media for a controlled TikTok experiment. Platform-quality statements will require retrieved-rendition evidence, not upload folklore.

    Is the app available?

    The public browser app is not available. The native CLI creates verified same-container fast-start copies, while browser/WASM processing remains planned.

    Why not just export at the highest bitrate?

    Platforms generate their own delivery versions. Uncrush treats the relationship between upload bitrate and delivered bitrate as a hypothesis until controlled rendition tests can measure it; file size alone is not evidence of viewer quality.

    Will the browser version process locally?

    That is the planned direction. The future browser processor is intended to run approved work on the device, but the current website does not process files.

    Preserve intent.

    Verify the file.

    Measure the result.