GET STARTED

Import

Import the canonical standalone control from its granular entry point.

import {
  NeuralFileUpload,
  type NeuralFileUploadValue,
} from '@neural-ng/core/file-upload';

Multiple files and Signal Forms

The model is always readonly File[]. Multiple mode appends accepted files without mutating the supplied array.

Single-file mode

Without multiple, the next accepted selection replaces the previous file while preserving the array-shaped model.

Angular Forms

Signal Forms, Reactive Forms and template-driven forms bind the same immutable file-array contract.

Client-side constraints

accept, size, count and duplicate checks produce deterministic rejection reasons. They improve UX but never replace server validation.

Control states

Readonly keeps the visible value inspectable while blocking mutation; disabled follows Forms ownership. Invalid, required and pending stay independent.

Labels, icons and compact list ownership

Every visible string can override the active locale and Neural Icons can be assigned without custom projected markup.

Application-owned HTTP upload

FileUpload has no URL, headers, authentication, progress, retry or chunking API. Build FormData and choose the transport in application code.

const body = new FormData();
for (const file of attachments()) {
  body.append('attachments', file, file.name);
}

http.post('/api/applications', body, {
  reportProgress: true,
  observe: 'events',
});

Unstyled and typed slots

Native chooser behavior, drag and drop, announcements and immutable state remain while consumer classes own every visual slot.

Native semantics

The native input retains accept, multiple, capture, name and FileList selection. The choose button targets it through aria-controls.

Names and status

Use Field composition, ariaLabel or ariaLabelledBy. Selection summaries and localized rejection messages are announced through a polite status region.

Keyboard behavior

Choose, remove and clear are native buttons, preserving Tab, Enter and Space. Focus returns to normal document order; drag-and-drop is never the only input path.

Security boundary

Browser MIME metadata and client limits are untrusted hints. Validate filename, size, content and authorization again on the server; never execute or preview untrusted files without a separate safe policy.

Inputs

Events

Methods

Typed class slots

Value and event contract

Every mode uses readonly File[]. Programmatic clear() and reset() do not impersonate user actions. User selection emits one detailed event even when all candidates are rejected.

Design tokens