Public image uploads must be treated as untrusted input. Validate the uploaded file type and size, generate a safe filename and store it through Laravel storage instead of trusting a filename supplied by the browser. Sensitive documents should use private storage and controlled download routes. Keep upload metadata separate from physical paths. A media record can include the storage disk, path, MIME type, dimensions and alternative text. Applications can then resolve public URLs from the configured filesystem disk instead of storing environment-specific localhost URLs throughout the database. On deployment, confirm the storage directory is writable, the public storage symlink exists, and APP_URL uses the real HTTPS backend address. Test the exact link in a private browser session. If the server domain changes, relative storage paths are easier to migrate than absolute URLs. Deletion also needs care. An image may be referenced by a project, blog post, logo or testimonial. Remove the reference before deleting the underlying asset, and prevent accidental deletion of media still used in published content.