◐ WIPE EFFECT
PING: -- ms
← Back to Articles

Introducing Load Light: Browser-Based Media Prep

Batch images and video, build responsive outputs, and give front-end tools or LLMs a clean map of the results.

Hero videos, full-width photography, responsive image sets, and mobile layouts can turn media prep into a separate job at the end of a build. Every file needs the right dimensions, compression, name, and markup before it is ready to ship.

Load Light puts that work in the browser. Drop in a mixed batch of images and video, choose how you want it processed, and export a lighter set of files with the metadata needed to place them on a site. You do not have to resize and document each asset by hand or open a traditional editing application for every pass.

What Load Light handles

Load Light accepts:

  • video files
  • still image files

It identifies each file type after import, so portrait images, landscape images, and motion clips can stay together in the same session. The batch tools cover:

  • media grouping
  • output formatting
  • responsive size generation
  • estimated payload reduction
  • metadata extraction
  • HTML reference generation
  • token-optimized JSON for LLM workflows

Step 1: Bring in your media

Start by adding files to the media panel. You can:

  • drag clips directly into the media panel
  • import assets from local storage

Load Light analyzes the files and separates still-image processing from video processing. You can see what is in the batch before setting up the export.

Load Light preset strip in the lower-left corner showing one-click web video and image sizing presets
Premade presets speed up typical web video and responsive image jobs.

Step 2: Set up the output

The panel on the right controls:

  • output quality
  • target dimensions
  • compression behavior
  • delivery intent
  • media export rules

You can tune those settings for the files you are making, whether the batch is headed for:

  • website hero media
  • gallery thumbnails
  • background loops
  • inline article images
  • responsive mobile assets

A single source can produce the different asset weights needed by a responsive front end.

Step 3: Start with a preset

The preset strip in the lower-left corner gives you a quick starting point for:

  • standard web video compression
  • common responsive image sizing
  • lightweight media delivery

Use a preset for a fast pass, then adjust the individual controls when the job needs something more specific.

Load Light browser workspace showing imported video and image thumbnails in the media panel with analysis in progress
Load Light after import: mixed media in the panel, ready for batch settings.

The work runs on your machine

Load Light runs in the browser, but it is not a cloud renderer. Your computer still decodes and processes the imported media.

Large, high-bitrate .MOV files can be demanding, especially on an older laptop or a slower system. Heavy video batches may cause:

  • increased RAM usage
  • browser fan spin-up
  • longer processing on very large batches

Still images are generally lighter work and process more quickly, including in larger batches. The exact wait still depends on your machine.

Mix aspect ratios in one batch

You do not have to split portrait and landscape media into separate jobs. One batch can contain:

  • vertical assets
  • horizontal assets
  • stills
  • motion

That keeps responsive media libraries with several orientations in one working session.

Export an HTML media reference

Load Light also generates an HTML reference snippet for the processed batch. It keeps:

  • file references
  • generated dimensions
  • asset metadata
  • delivery information

The markup gives you an implementation reference for dimensions, output names, and media order when you build the final tags.

Give LLMs a media map with AI Max

AI Max packages the full batch as one token-optimized JSON structure for an LLM to read. Each asset is mapped to a consistent schema, responsive sizes are grouped in nested arrays, and the export includes dominant color palettes.

The HTML reference is ready-made markup for a developer. AI Max carries more context in a machine-readable form. A coding assistant can inspect the JSON to see which assets exist, how their responsive versions relate, and which file to reference without searching through the media folder or reconstructing the batch from filenames.

AI Max does not change the compression pass or create a lighter media file. It creates a compact reference for LLM-assisted work, which matters most when a project has a large batch and several versions of each asset.

Use standard or custom sizes

Choose the standard responsive outputs or enter the dimensions required by a custom breakpoint:

  • standard web-ready outputs
  • manually defined custom dimensions

Read estimated savings as a batch total

The estimated savings readout shown in the tool is a batch total.

It does not show the reduction for an individual file. If the session contains ten assets, the number reflects the projected payload reduction across all ten processed outputs.

Audio passes through unchanged

Load Light currently preserves source audio without adding controls for:

  • audio compression
  • volume processing
  • audio stripping
  • format changes

The exported output keeps the audio from the imported source. Dedicated audio controls are planned for a future update; the current tool focuses on visual media.

Where Load Light fits

Load Light is a batch-prep utility, not a replacement for editorial software. It sits between raw asset collection and web deployment. Use it as:

  • a media prep station
  • a responsive asset generator
  • a payload reduction utility
  • a metadata reference builder

For image work, that can be a quick trip through a preset and an export. Video takes more planning: source bitrate, batch size, and the computer doing the processing all affect the wait. Either way, the files leave the browser organized, documented, and ready for the next step in the build.


VIEW MORE WORK