Weave Code
Laravel Tus Upload Laravel Package
oneofftech/laravel-tus-upload
Add tus.io resumable uploads to Laravel. Provides an upload endpoint, upload lifecycle management, and events so large files can resume after network drops and integrate cleanly with your app's storage and authorization.
A package for handling resumable file uploads in a Laravel application via the http://tus.io/ resumable file upload protocol.
Frequently asked questions about Laravel Tus Upload
- How do I install oneofftech/laravel-tus-upload in a Laravel app?
- Install it with Composer using composer require oneofftech/laravel-tus-upload, then publish the package configuration and any migrations it ships. Register the package routes and middleware so the tus upload endpoint is reachable, and point it at the storage disk you want uploads written to. Plan a short spike first, since endpoint behavior and storage-driver support should be validated before you commit to the integration.
- Which PHP and Laravel versions does laravel-tus-upload support?
- Release v0.11.0 dropped PHP 7.4 and earlier, so PHP 8.0+ is a hard requirement. Laravel 9 is the version explicitly confirmed by the release notes; Laravel 8 and Laravel 10+ are not claimed, so verify compatibility on your target framework before adoption. Every environment, including CI, must be on PHP 8.0 or newer.
- Does laravel-tus-upload work with S3 or other Laravel storage disks?
- The package is built on top of Laravel's storage and filesystem abstractions rather than a separate upload service, so it should fit conventional disk configuration. That said, storage-driver support is not explicitly documented in the release notes, and tus chunking can behave differently on remote object stores than on local disks. Validate your chosen driver, such as local or an S3-compatible disk, with a multi-gigabyte test upload before locking the design.
- What frontend tus client do I need for laravel-tus-upload?
- You need a tus-compatible client in your frontend, for example the official tus-js-client, because the browser's standard form upload cannot speak the protocol. The package provides the server endpoint, not the client, so budget UI work for chunking, retries, and progress reporting. Confirm which tus protocol version and JS client release the package expects before building that layer.
- How does resumable upload work if the network drops mid-upload?
- The tus protocol tracks upload offsets, so when a connection fails the client can query the server for the bytes already received and continue from that point instead of restarting. laravel-tus-upload handles that server-side lifecycle, including the upload endpoint and the state needed to resume. You should still prove it in your own environment by starting a large upload, killing the connection, and confirming the resume succeeds with an intact file.
- Is laravel-tus-upload production ready given it is still 0.x?
- It is a thin protocol layer with a small surface area, which keeps operational overhead low, but the 0.x versioning means minor releases can include breaking changes, as v0.11.0 did with the PHP requirement. Pin the exact version in composer.json and treat upgrades as planned work with regression testing rather than routine composer update. The package is also driven by a small maintainer group, so assess bus factor and release cadence before making it a production dependency.
- How do I authorize uploads with laravel-tus-upload?
- Because the package sits on Laravel's routing and middleware, upload endpoints can be protected with your existing auth and authorization middleware. The package provides upload lifecycle management and events, which you can use to bind uploads to a user, tenant, or model and to run post-upload processing. Decide early whether authorization happens at upload creation, per chunk request, or both, and test unauthenticated and cross-tenant requests.
- How should I test resumable uploads in a Laravel application?
- Run a timeboxed spike: install the package, upload a multi-gigabyte file, terminate the connection mid-transfer, and confirm the client resumes from the correct offset. Also check failure cases such as expired uploads, mismatched offsets, and duplicate or partial files landing on your disk. Add automated coverage around your upload endpoint and middleware, and keep the manual large-file test as part of your upgrade checklist.
- How do I upgrade from v0.10.x to v0.11.0 of laravel-tus-upload?
- Upgrade all environments and CI to PHP 8.0+ first, then align with Laravel 9 and update the Composer constraint. Re-publish the package configuration and migrations if the release changes them, and regression test the upload endpoints end to end. Beyond the PHP and framework bumps there is no published step-by-step upgrade guide, so review the changelog and verify your stored upload layout and any package-owned tables.
- When should I avoid laravel-tus-upload, or what alternatives exist?
- Skip it if you only handle small files on stable connections, since standard Laravel file uploads are simpler and need no extra client. It is also a transport layer only, so do not adopt it expecting media processing, virus scanning, or file management features. If you want a standalone server rather than a Laravel package, a self-hosted tusd deployment is a common alternative, at the cost of running extra infrastructure.
Weaver
How can I help you explore Laravel packages today?