ImageField y servicio de cargas

For pictures, use ImageField instead of FileField. It works the same but adds image-specific checks and helpers on top.

ImageField depends on the Pillow library to read images. Install it first or migrations will refuse to run. 🖼️

ImageField verifies an upload is a real image. A renamed .txt file gets rejected during form validation automatically.

Set width_field and height_field and Django records each image's dimensions into those columns on save.

In a template, point an img tag at the field's .url to render the stored picture for the user.

Calling .url on an empty field raises an error. Wrap it in an if check so missing images do not crash your page.

Give the field a default image path so users without an upload still see a placeholder avatar.

Django will not serve media on its own. In development, add a route from MEDIA_URL to MEDIA_ROOT in your project urls.

That media helper is for development only. In production a real web server serves uploads, so guard the route with a DEBUG check.

In production let Nginx or a storage service like S3 serve media directly. Routing every image through Django would be slow.

Need resized versions? Libraries like django-imagekit generate thumbnails on top of ImageField when you are ready.

You learned that ImageField needs Pillow, validates real images, exposes .url for display, and that production should serve media outside Django. 🎉