Blog

How to Bulk Resize and Compress Images in Airtable

FE
Filla EditorialintermediateMar 19, 2026

How to Bulk Resize and Compress Images in Airtable

Airtable accepts image uploads of any size. A table collecting product photos, design submissions, field documentation, or headshots through forms can quickly accumulate gigabytes of full-resolution images. These oversized files cause problems downstream:

  • Airtable bases slow down when attachment-heavy tables load
  • Gallery views render slowly with high-resolution thumbnails
  • Sharing images from Airtable to web applications or reports requires manual resizing
  • Storage costs increase for integrations that sync Airtable attachments
  • Email-based workflows fail or are delayed by large image attachments

Airtable has no built-in image processing. There is no way to resize, compress, or convert an image stored in an attachment field without downloading it, processing it in external software, and re-uploading it. For a table with hundreds of image records, this is not a viable workflow.

Filla's Image Manipulator is a processor tool that resizes, compresses, and converts images stored in Airtable attachment fields -- in bulk, in the background, with full control over dimensions, quality, and output format.

Managing images in Airtable Filla's Image Manipulator bulk resizes, compresses, and converts images in your attachment fields

Start free

What the Image Manipulator does

The tool runs a three-stage processing pipeline on every image in the selected attachment field:

  1. Resize -- Change image dimensions using exact sizes, maximum constraints, percentage scaling, or presets.
  2. Compress -- Reduce file size through quality adjustment or lossless compression.
  3. Convert -- Change the image format (JPEG, PNG, WebP, GIF, TIFF).

Each stage is optional and independently toggleable. You can resize without compressing, compress without resizing, convert without changing dimensions, or combine all three operations.

The tool processes image types: JPEG, PNG, WebP, GIF, TIFF, BMP, and SVG. Non-image attachments (PDFs, documents, videos) in the same field are automatically skipped.


Step-by-step: Resize and compress Airtable images

Step 1: Identify the attachment field

Open your Airtable table and find the attachment field containing the images you want to process. Note whether you want processed images written back to the same field or a different one.

Step 2: Create an Image Manipulator tool in Filla

In your Filla workspace, open the base containing the images. Create a new processor tool and select Image Manipulator. Name it something like "Product Image Optimization" or "Headshot Standardization."

Step 3: Configure source and output fields

Select the source table and source attachment field (where the original images are stored). Then select the output attachment field where processed images will be saved.

The output field can be the same as the source field -- if you enable the "Overwrite Source Field" option, the originals are replaced with the processed versions. If you use a different output field, originals are preserved and processed versions are written to the new field.

Step 4: Configure resize settings (optional)

Enable resize and choose a resize mode:

Max Dimensions: Set a maximum width and/or height in pixels. Images larger than these dimensions are scaled down proportionally. Images already smaller than the maximums are left unchanged (unless you enable "Allow Upscaling"). This is the most commonly used mode for standardizing image sizes across a table.

Exact Size: Specify exact width and height. Choose a fit mode to control how images are adjusted:

  • Contain: The entire image fits within the dimensions (may add padding).
  • Cover: The image fills the dimensions (may crop edges).
  • Fill: The image is stretched to fill exactly (may distort).

Percentage: Scale all images to a percentage of their original size. Setting 50% makes every image half its original dimensions.

Preset: Quick selection of common sizes:

  • Thumbnail (150x150)
  • Web (1200x800)
  • Social (1080x1080)
  • HD (1920x1080)

The Allow Upscaling option controls whether images smaller than the target size are enlarged. For most use cases, leave this off to avoid blurry upscaled images.

Step 5: Configure compression settings (optional)

Enable compression and set the quality level from 1 to 100. Lower values produce smaller files with more visible compression artifacts. For most use cases:

  • 80-90: Excellent quality, noticeable file size reduction. Best for web and general use.
  • 60-79: Good quality, significant size reduction. Suitable for thumbnails and previews.
  • Below 60: Visible quality loss. Only use when file size is the primary concern.

For PNG images specifically, enable Lossless Compression to reduce file size without any quality loss. Lossless compression achieves less dramatic size reduction than lossy compression but preserves the image perfectly.

Step 6: Configure format conversion (optional)

Enable format conversion and choose the output format:

  • JPEG: Best for photographs. Smallest file sizes with lossy compression. No transparency support.
  • PNG: Best for graphics, screenshots, and images requiring transparency. Larger file sizes.
  • WebP: Modern format with excellent compression and transparency support. Smaller than JPEG at equivalent quality. Not supported by all legacy systems.
  • GIF: Limited to 256 colors. Use only for simple animations or very simple graphics.
  • TIFF: High-quality format for print production. Large file sizes.

Converting from PNG to JPEG is a common optimization for photographs that were uploaded as PNGs. Converting to WebP offers the best file size reduction for web-bound images.

Step 7: Configure execution settings

  • Overwrite Source Field: When enabled, replaces original images with processed versions. When disabled, processed images are written to the output field alongside the originals (or to a separate field).
  • Batch Size: Number of records processed per batch. The default works well for most tables.
  • On Error: Choose how errors are handled -- stop processing entirely, continue with the next record, or skip the failed record.

Step 8: Run the Image Manipulator

Click Run to start processing. The tool downloads each image, runs it through the resize/compress/convert pipeline, uploads the processed version, and writes it back to the Airtable attachment field.

Real-time progress tracking shows records processed, succeeded, and failed. The execution log reports compression savings -- original file size versus processed file size -- so you can see exactly how much space was saved.


Common use cases

Standardizing form submission photos

Filla's form builder lets you collect images through attachment fields with configurable file type restrictions and size limits. But even with a 50MB file size limit, users submit images at wildly different resolutions. Run the Image Manipulator to standardize all submitted photos to consistent dimensions and quality after collection.

Optimizing product catalog images

E-commerce teams storing product photos in Airtable need web-optimized images. Use Max Dimensions (1200x800) with JPEG compression at quality 85 to produce images that load quickly on product pages without visible quality loss.

Creating thumbnails

Need small preview images alongside your originals? Set the output to a different attachment field, use the Thumbnail preset (150x150), and run. Your original high-resolution images are preserved while thumbnails are generated in a separate field.

Converting to WebP

WebP images are 25-35% smaller than equivalent JPEG files at the same visual quality. If your images are destined for web display, convert them to WebP for faster page loads and lower bandwidth costs.

Reducing Airtable base size

If your Airtable base is sluggish due to large attachment sizes, compress existing images to reduce the total storage footprint. Use quality 80 with the Overwrite Source Field option to replace bloated originals with optimized versions.


Processing pipeline details

Understanding the pipeline order helps you predict results:

  1. Resize runs first. The image is resized to target dimensions before any compression is applied.
  2. Compression runs second. Quality reduction is applied to the resized image.
  3. Format conversion runs last. The compressed, resized image is converted to the target format.

This means compression quality settings apply to the resized image, not the original. Resizing an image down before compressing it produces better visual results at the same quality level, because the compression algorithm works with fewer pixels.


FAQ

What image formats are supported?

The Image Manipulator processes JPEG, PNG, WebP, GIF, TIFF, BMP, and SVG files. Non-image attachments (PDFs, videos, documents) in the same field are automatically skipped.

Can I process images in multiple attachment fields at once?

Each Image Manipulator tool processes one source attachment field. To process multiple fields, create a separate tool for each field. This gives you independent control over the processing settings for each field.

Will processing lose my original images?

Only if you enable "Overwrite Source Field" and use the same field for source and output. To preserve originals, either use a different output attachment field or leave the overwrite option disabled.

How long does processing take?

Processing time depends on image sizes, the number of images, and which operations are enabled. Resize and compression are handled by the Sharp image processing library and are fast even for large images. A table with 500 standard-resolution photos typically processes in a few minutes.

Can I set up recurring image processing?

The Image Manipulator runs manually from the Filla dashboard. For tables that receive new images regularly (through form submissions, for example), run the tool periodically. Use record filters or source views to process only new records that have not been processed yet.


Optimized images for Airtable workflows

Oversized images slow down Airtable, increase storage costs, and create friction in downstream workflows. Filla's Image Manipulator gives Airtable teams direct control over image dimensions, quality, and format -- applied in bulk across entire tables.

Try the Image Manipulator → or explore all of Filla's Airtable processor tools.

Ready to build smarter Airtable workflows? Start with Filla's form builder -- forms, processor tools, and document generation, all Airtable-native.