Use local storage when files should live directly on the same server or filesystem path the app controls.

• single-server installs
• simple deployments
• operators who want direct filesystem visibility
• installs using Nginx, Apache, or LiteSpeed handoff against local paths

1. Open Storage Nodes.
2. Add a local node.
3. Set the storage path carefully.
4. Choose the delivery method.
5. Test the node.
6. Upload and download a real file.

• keep the storage path outside public browsing paths unless the delivery method explicitly expects a served path
• verify PHP and web-server permissions before blaming the app
• treat delivery-method changes as infrastructure changes, not cosmetic edits

Local Storage now works with the modern multipart uploader through an app-routed upload path.

That means:

• large local uploads should no longer fail just because global chunked uploads are enabled
• local uploads are not using bucket CORS rules like Wasabi, B2, or R2
• if a local upload fails, permissions, route availability, PHP limits, and server body-size limits matter more than object-storage settings

• verify the storage path is writable by PHP
• verify the app can write to its private multipart temp area too
• upload one file larger than a single chunk
• then download that file through the live site

• Nginx Setup
• Uploads and Downloads
• Storage Nodes