Uploading Assets

Where to upload

Click Upload in the sub-navigation at Setup → Media Hub → Upload, or use the upload button within the library view. Both routes open the same uploader.

Adding files

Drag and drop files onto the upload area, or click to browse and select them. Multiple files can be dropped together for batch upload.

From 1.19.25, selected files appear in a scrollable card queue. Each card shows a file-type icon or lazy thumbnail preview for images, inline status, and progress bar. Filenames can be edited inline on each card before upload.

Organise before upload

Above the dropzone, the Organise uploads bar lets you assign collections and labels before the batch starts. Use the gear icon to reveal upload settings; the panel stays hidden until you add files or open it manually.

Selected collections and labels appear as dismissible pills in a summary strip when the settings panel is closed. When auto-crop presets are configured in module settings, a Crops button shows how many will run (informational only).

During upload

A master progress bar shows file count and byte-weighted percentage across the batch. You can cancel mid-batch: in-flight files return to pending; completed files stay done. Individual failed files offer retry or remove actions. Oversized files are staged with a clear warning but excluded from upload.

When the batch completes, the queue header badge turns green and reads how many uploads finished. Use Add more to queue additional files without leaving the page.

Validation

Files are validated against two module-level settings (configurable in Configuration):

• Allowed file extensions - files with unlisted extensions show Unsupported type on the card
• Maximum upload size - files exceeding the limit are rejected

Images exceeding your configured maximum dimensions are automatically resized at upload time.

SVG uploads are disabled by default. To enable them, install FileValidatorSvgSanitizer and tick Allow SVG uploads in module config. See Configuration → SVG Support.

Thumbnails at upload (1.19.25)

Upload creates one small proportional preview per image for inputfield cards, not four separate sizes (grid, retina grid, list, and inputfield preview). That is three fewer files per image (75% less): 100 uploads means 100 thumbnail files, not 400.

Grid, Masonry, and List share one canonical library thumbnail per asset. The full library size is generated on first browse as you scroll, not during upload. Import Existing Images follows the same on-demand model. Tiles use lazy loading and show the upload preview or a placeholder while the library size is prepared.

Automatic collection assignment

If you navigate to Upload from within a collection (for example via the empty-state button inside a collection view), all uploads in that session are automatically assigned to that collection. You can also pick collections and labels explicitly in the Organise bar before starting the batch.

Uploading from a page editor

From MediaHub 1.19.0, editors can upload directly into a MediaHub field on any page edit screen without opening the library first.

• Drag files onto the field (the whole field is the drop target, with the same blue highlight as ProcessWire's native Images field)
• Or click Upload beside Media Hub in the field toolbar

Uploads use the same validation and pipeline as Setup → Media Hub → Upload. New cards appear immediately with crop, focus, and edit actions; the page does not need to be saved first for the cards to show. Progress appears on each placeholder card; Save is disabled while uploads are in progress.

Supported types match the field's asset filter: images, PDFs, video, audio, and documents when All types is selected. Fields set to Images only reject non-image drops with an inline notice.

Per-field control: Setup → Fields → [field] → Input → Media Hub Picker Settings → Direct file upload. Enabled by default; turn it off when editors should only pick existing library assets (for example a strictly curated hero field).

Works inside Repeater and RepeaterMatrix items. Multi-file drops respect the insertion position when the field already contains assets (same marker behaviour as drag-to-reorder).