Upload handling

When a new asset lands in Pixelbin, a Beam agent reads the file and its metadata. It applies your approved rule to generate the resized, compressed, or reformatted variants your channels need, then writes them back and records where each one lives. Standard images that fit a known preset are handled on their own. A file with an unexpected format, a corrupt upload, or dimensions that break a preset is held, and the agent notifies an operator with the issue named, so a person decides how to handle the odd asset before it reaches a live surface.

Resizing and format presets

Every channel wants its own size. On a triggering upload or request, the agent reads the source image, applies your preset rule to produce the exact dimensions and formats each destination requires, and writes the variants into the asset record. Requests that map to an existing preset run without review. When a request calls for a preset that does not exist, would enlarge past a quality limit, or conflicts with brand crop rules, the agent asks a designer to confirm, so a new preset stays a human choice rather than quietly multiplying inconsistent versions across your whole library.

Compression and quality checks

Smaller files load faster, but only to a point. After a variant is made, the agent reads the output size and applies your quality rule to accept it or try a different setting. Variants that meet your size and clarity targets are written to the asset record automatically. An image where compression introduces visible artifacts, misses the size budget, or fails a quality check is set aside for a person to review, so the library never fills with degraded pictures that a rule judged acceptable but a human eye would plainly reject.