Upload
- Usage
- Styling
- File Handling
Upload allows the user to upload files, giving feedback to the user during the upload process. It shows the upload progress and the status of each file. Files can be uploaded by clicking on the Upload button, or by dragging them onto the component.
new tab
<!-- Use the target attribute to specify the URL
that handles the file upload -->
<vaadin-upload
target="/api/fileupload"></vaadin-upload>
Drag & Drop
Upload allows the user to drag files onto the component to upload them. Multiple files can be dropped simultaneously. By default, this is enabled on desktop computers, and disabled on touch devices. Explicitly setting it to enabled or disabled, though, affects both desktop and mobile devices.
new tab
<label for="upload-drop-enabled">Drag and drop enabled</label>
<vaadin-upload id="upload-drop-enabled" .nodrop="${false}"></vaadin-upload>
<label for="upload-drop-disabled">Drag and drop disabled</label>
<vaadin-upload id="upload-drop-disabled" nodrop></vaadin-upload>
Auto-Upload
By default, files are uploaded immediately — or at least they’re added to the queue to be uploaded. Auto-upload can be disabled, for example, to allow the user to review the list of files before initiating their upload by clicking the ▶️ button for each file. Change the button label, though, to indicate that uploads don’t start automatically.
new tab
@query('vaadin-upload')
private upload!: Upload;
protected override firstUpdated() {
this.upload.i18n.addFiles.many = 'Select Files...';
this.upload.i18n = { ...this.upload.i18n };
}
protected override render() {
return html`
<vaadin-upload
no-auto
></vaadin-upload>
`;
}
Uploads can be initiated programmatically when auto-upload is disabled. You might do this, for example, if you want to provide the user with a single button to start all uploads.
new tab
@query('vaadin-upload')
private upload!: Upload;
protected override render() {
return html`
<vaadin-upload
no-auto
></vaadin-upload>
<vaadin-button theme="primary" @click="${this.uploadFiles}"> Upload All Files </vaadin-button>
`;
}
uploadFiles() {
this.upload?.uploadFiles();
}
Upload Restrictions
You can set three types of restrictions: file format; file count; and file size.
Exceptions that arise — usually from the user violating any of the imposed restrictions — aren’t shown in the UI by default. Use a File Rejected listener to catch those exceptions and, for example, a Notification to inform the user of the problem, together with any potential solutions.
The user should be informed upfront, though, about any file upload restrictions. Limitations on the maximum number of files allowed, file size, and format should all be communicated clearly, to reduce or eliminate exceptions.
File Format
Upload can be configured to accept only files of specific formats. The acceptable file formats are set using MIME type patterns or file extensions (e.g., "video/*"
, "image/tiff"
or ".pdf"
and "audio/mp3"
).
new tab
<h4>Upload report</h4>
<p>Accepted file formats: PDF (.pdf)</p>
<vaadin-upload
accept="application/pdf,.pdf"
max-files="1"
@file-reject="${(event: UploadFileRejectEvent) => {
Notification.show(event.detail.error);
}}"
></vaadin-upload>
Note
|
Prefer MIME Type
Although MIME types are widely supported, file extensions are only implemented in certain browsers and should be avoided.
|
Note
|
File Format Restrictions are Client-Side
File format restrictions set with Using this method won’t restrict the uploaded file’s format on the server side. The Upload component doesn’t have an API to restrict uploaded files by file format or content on the server side. If required, it’s the responsibility of the application developer to implement application-specific restrictions on the server side in one or more of the Upload component’s event listeners (e.g., in |
File Count
By default, Upload doesn’t limit the number of files that can be uploaded. However, you can set a file count limit. If you set the maximum to one, the native file browser prevents multiple files from being selected.
Note
|
Java Flow-Specific
When using a Receiver that doesn’t implement the MultiFileReceiver interface — such as MemoryBuffer or FileBuffer — the Upload component limits the number of files to one. This is because these receiver implementations only support handling a single file at once.
|
new tab
protected override render() {
const maxFiles = 3;
return html`
<h4>Upload files</h4>
<p>Maximum of ${maxFiles} files allowed</p>
<vaadin-upload
.maxFiles="${maxFiles}"
@file-reject="${(event: UploadFileRejectEvent) => {
Notification.show(event.detail.error);
}}"
></vaadin-upload>
`;
}
File Size
Upload allows you to limit the file size by setting a maximum amount in bytes. By default, though, there is no limit.
new tab
protected override render() {
const maxFileSizeInMB = 10;
const maxFileSizeInBytes = maxFileSizeInMB * 1024 * 1024;
return html`
<h4>Upload file</h4>
<p>Maximum file size: ${maxFileSizeInMB} MB</p>
<vaadin-upload
max-files="1"
.maxFileSize="${maxFileSizeInBytes}"
@file-reject="${(event: UploadFileRejectEvent) => {
Notification.show(event.detail.error);
}}"
></vaadin-upload>
`;
}
Note
|
Revalidate Size Limit on Server
This constraint is set on the client and is checked before contacting the server.
|
File Actions
Each file has a certain set of associated actions available, depending on its upload state. A file always has a Clear/Remove button. This button cancels the upload if applicable, and removes the file from the list. This button is the only available action during and after a successful upload.
new tab
import React from 'react';
import { useComputed } from '@vaadin/hilla-react-signals';
import { Upload } from '@vaadin/react-components/Upload.js';
import { createFakeUploadFiles } from './upload-demo-helpers';
function createFakeFiles() {
return createFakeUploadFiles([
{
name: 'Workflow.pdf',
progress: 60,
status: '19.7 MB: 60% (remaining time: 00:12:34)',
},
{ name: 'Financials.xlsx', complete: true },
]);
}
function Example() {
const files = useComputed(createFakeFiles);
return <Upload files={files.value} />;
}
Note
|
Remove the File
The Clear/Remove button doesn’t remove a successfully uploaded file from the server file system or database. It’s only removed from the file list. Remember to remove the file from the backend.
|
If an error or exception occurs, Upload displays a Retry button for the user to be able to try to upload the file again.
When a file is queued (i.e., auto-upload is disabled), there’s a Start Button that the user must press to begin the upload process.
Internationalization (i18n)
All labels and messages in Upload are configurable. For a complete list of them, see the API documentation (Java and Web component).
new tab
protected override render() {
const i18n: UploadI18n = {
dropFiles: {
one: 'Raahaa tiedosto tähän',
many: 'Raahaa tiedostot tähän',
},
addFiles: {
one: 'Valitse tiedosto...',
many: 'Valitse tiedostot...',
},
error: {
tooManyFiles: 'Liian monta tiedostoa.',
fileIsTooBig: 'Tiedosto on liian suuri.',
incorrectFileType: 'Väärä tiedostomuoto.',
},
uploading: {
status: {
connecting: 'Yhdistetään...',
stalled: 'Pysäytetty',
processing: 'Käsitellään tiedostoa...',
held: 'Jonossa',
},
remainingTime: {
prefix: 'aikaa jäljellä: ',
unknown: 'jäljellä olevaa aikaa ei saatavilla',
},
error: {
serverUnavailable: 'Palvelin ei vastaa',
unexpectedServerError: 'Palvelinvirhe',
forbidden: 'Kielletty',
},
},
units: {
size: ['t', 'kt', 'Mt', 'Gt', 'Tt', 'Pt', 'Et', 'ZB', 'YB'],
sizeBase: 1000,
},
};
return html`<vaadin-upload .i18n="${i18n}"></vaadin-upload>`;
}
Customization
You can replace the default upload button. You might do this if Upload needs a stronger emphasis. If so, you can use a primary button.
new tab
<vaadin-upload
max-files="1"
accept="application/pdf,.pdf"
@file-reject="${this.fileRejectHandler}"
@max-files-reached-changed="${(event: UploadMaxFilesReachedChangedEvent) => {
this.maxFilesReached = event.detail.value;
}}"
>
<vaadin-button slot="add-button" theme="primary" ?disabled="${this.maxFilesReached}">
Upload PDF...
</vaadin-button>
</vaadin-upload>
You can also customize the drop label, as well as the icon.
new tab
<vaadin-upload>
<vaadin-icon slot="drop-label-icon" icon="vaadin:cloud-upload-o"></vaadin-icon>
<span slot="drop-label">
Files will be uploaded to our cloud. See our
<a href="https://vaadin.com/privacy-policy" target="_blank">privacy policy</a>
</span>
</vaadin-upload>
Tip
|
Large Drop Target
When customizing the Upload component, make sure not to make the drop target too small. A large drop target is easier to use and less error-prone.
|
Listeners
Upload has listeners for the following events:
- All Finished
-
Triggered when Upload has processed all of the files in its queue, regardless of whether all uploads were successful.
- Failed
-
Occurs when the upload is received, but the reception is interrupted for some reason.
- File Rejected
-
Sent when the file selected for upload doesn’t meet the constraints (e.g., file size limit).
- Finished
-
Sent when Upload receives a file, regardless of whether the upload was successful. To distinguish results, use instead either Succeeded or Failed listeners.
- Progress
-
Event for tracking upload progress.
- Started
-
Triggered when the upload starts.
- Succeeded
-
Sent when the upload has been received successfully.
Best Practices
With regards to developing with Upload, this section provides some suggestions on how to label buttons and how to construct error messages for better user experiences.
Labeling
Choose labels that are informative and instructive. For example, if the user is to upload a single PDF file, it’s better to have the button label say "Upload PDF…" instead of "Upload File…". The task becomes clearer and improves accessibility for the user — especially if they’re using a screen reader, as the button’s label is read aloud when focused.
new tab
protected override firstUpdated() {
this.upload.i18n.addFiles.one = 'Upload PDF...';
this.upload.i18n.dropFiles.one = 'Drop PDF here';
this.upload.i18n.error.incorrectFileType =
'The provided file does not have the correct format (PDF document).';
this.upload.i18n = { ...this.upload.i18n };
}
protected override render() {
return html`
<vaadin-upload
max-files="1"
accept="application/pdf,.pdf"
@file-reject="${this.fileRejectHandler}"
></vaadin-upload>
`;
}
Likewise, if the user is expected to upload a spreadsheet, but multiple file formats are accepted, label the button, "Upload Spreadsheet". Include helpers to inform the user which formats are accepted.
new tab
protected override firstUpdated() {
this.upload.i18n.addFiles.one = 'Upload Spreadsheet...';
this.upload.i18n.dropFiles.one = 'Drop spreadsheet here';
this.upload.i18n.error.incorrectFileType =
'Provide the file in one of the supported formats (.xls, .xlsx, .csv).';
this.upload.i18n = { ...this.upload.i18n };
}
protected override render() {
return html`
<h4>Upload spreadsheet</h4>
<p>
File size must be less than or equal to ${maxFileSizeInMB} MB.<br />
Only Excel and CSV files are accepted.
</p>
<vaadin-upload
max-files="1"
.maxFileSize="${maxFileSizeInBytes}"
.accept="${acceptedTypes.join(',')}"
@file-reject="${this.fileRejectHandler}"
></vaadin-upload>
`;
}
Error Messages
Try to provide meaningful feedback and error messages when an exception or error occurs. Avoid technical jargon. Instead, try to provide solutions and instructions on how to fix the error.
A "Server Unavailable" message might suffice for tech-savvy users, but for some it might be lacking, unhelpful, and frustrating. Error messages should be written with your users in mind.
new tab
protected override firstUpdated() {
this.uploadRecommended.i18n.uploading.error.unexpectedServerError =
"File couldn't be uploaded, try again later";
this.uploadRecommended.i18n = { ...this.uploadRecommended.i18n };
}
protected override render() {
return html`
<vaadin-upload
id="upload-recommended"
nodrop
></vaadin-upload>
`;
}