ezav
Join the waitlist →

Encoder setup & help.

01 / PREFLIGHT

Catch delivery issues early.

Check the video dimensions and frame rate before conversion. Dimensions outside a 4-pixel block need an explicit padding choice; the app does not silently crop your canvas.

02 / PLAYBACK BUDGET

Connect encoding to storage.

See a texture baseline and a sustained drive budget with your reserved capacity. Large packages include guidance on the 10GbE transfer path. Estimates remain separate from actual encoded file measurements.

03 / HANDOVER

Deliver more than a MOV.

Each finished file gets a JSON report with the checked format, dimensions, frame rate, file size, SHA-256 and estimated transfer times. Choose full-video decode verification for an additional output check.

Convert MP4 or MOV to HAP in four steps.

  1. Install once. Run ezav setup. It installs the application, verifies and sets up the encoding engine, and adds a Start menu shortcut. There is no ZIP to unpack or engine executable to locate.
  2. Add your videos. Drop local files into the queue or choose Add videos. MP4 and MOV are common inputs; other supported formats depend on the installed engine.
  3. Choose the HAP format. Select HAP, HAP Q or HAP Alpha. Output saves beside the original videos by default, or you can choose a different folder. Advanced controls are in Settings.
  4. Start encoding. The app checks the media, converts it, verifies the output and writes a JSON delivery report. Original videos and existing outputs are never replaced.

Setup checks saved engine preferences, the existing ezav engine and PATH for HAP support before downloading. It can reuse that engine, use ffmpeg-9.0.2-full_build-shared.7z beside the installer, or download the pinned build and verify its SHA-256. Existing ezav installations can be updated without removing your videos. Cancel and close ask for confirmation during installation. FFmpeg is a separate project; its notices are retained with the installed engine. If your Windows installation needs .NET Framework 4.8, use the Microsoft download page.

HAP encoding questions

What is the difference between HAP, HAP Q and HAP Alpha?

HAP uses a smaller color texture payload. HAP Q uses a higher-quality color representation and a larger baseline payload. HAP Alpha carries transparency. This preview supports those three output choices; it does not encode HAP Q Alpha, HAP R or HAP HDR. Confirm the format supported by your media server.

Can I convert MP4 to HAP Q?

Yes, when the selected FFmpeg engine can read the source. Choose HAP Q and export to MOV. Converting a compressed source does not recover detail already lost in the original; use the best source available.

Does HAP file size stay the same for every video?

The texture baseline follows resolution, frame rate and HAP variant. Optional Snappy compression depends on the encoded content, so actual file sizes can vary. The HAP bitrate and file-size calculator helps plan the baseline; the encoder report records the finished file.

Is my video uploaded?

No. The desktop application processes your files on your computer. Encoding speed depends on the selected engine, source and hardware. No cloud encoding service is used.

What happens to frame rate, transparency and audio?

Output is constant frame rate. Source-average mode uses the source’s reported average rate. Select HAP Alpha to retain transparency. Optional audio uses the first audio track and converts it to stereo PCM, 24-bit / 48 kHz; it does not preserve a multichannel mix or every source track.

Does a verified output guarantee smooth playback?

No. Output checks and full-video decoding help catch file problems, but they do not certify a particular media server. Test your actual media, layers, transitions, storage and outputs on the intended hardware. HDR metadata, rotation workflows and color-managed mastering are outside this preview’s scope.

Download details

Windows preview 0.4.0. No macOS or Linux build is available in this release. The application and installer are unsigned previews. Setup handles the engine automatically. Microsoft Store publishing or verified code signing is a separate release step.

Installer integrity: SHA-256 checksum. Compare the downloaded archive’s hash with this value: 08de50351103a9c6a00eb904feff00c19f1ea05710fd9835d966652762ff869e