Choose a CSV export when the recipient needs rows and columns to analyze or import. Choose an attachment download when they need the actual images, PDFs or other files stored in Airtable. When a handoff needs both the record context and the file contents, prepare both and check that they describe the same selection.
miniExtensions offers a CSV Exporter and Bulk Download Attachments, but they solve different problems. Neither should be described as a complete, restorable backup of an Airtable base. Start with what the recipient must do after receiving the handoff, not with which download button is easiest to find.
Use CSV when the next job is about record values
A fictional catalog manager sends an approved product list to a distributor. The distributor needs product references, descriptions and dimensions to map into another system. A CSV is the natural starting point because its rows and columns express those values without requiring someone to read them out of filenames.
The CSV export guide describes generating a CSV through an export URL. Decide which records and fields belong in that output. A source view can restrict rows, but field selection remains a separate configuration. Hiding an internal column in an Airtable view is not a substitute for checking the exporter’s chosen fields.
Inspect a sample in the receiving application. Product codes with leading zeros, dates and long identifiers deserve particular attention because the destination may interpret text differently. The receiving application may need its own import-format settings.
Use an attachment download when files are the deliverable
The same distributor’s designer may need product photos rather than a spreadsheet of descriptions. Bulk Download Attachments packages the selected attachment files into a ZIP. Its settings guide covers multiple attachment fields, folders and downloaded filenames.
Select only the attachment fields intended for this recipient. A record may contain approved product photos and separate internal reference files. Choosing the right records is not enough if the configuration also includes an unintended attachment field.
Use a stable product reference in the folder naming scheme rather than relying on display names that may repeat. Open representative files after extracting the archive. A ZIP that downloads successfully can still contain the wrong revision or an unhelpful folder arrangement. The project attachment handoff tutorial provides a fuller walkthrough for building and inspecting a file package.
Do not mistake attachment URLs for downloaded files
The decisive difference is explained in the CSV attachment documentation: attachment columns contain links, not embedded PDFs or image bytes. A spreadsheet with populated attachment cells is therefore not an offline copy of those files.
If the distributor needs to work without opening Airtable attachment URLs later, send the actual files through an appropriate delivery process. Do not ask them to discover after a deadline that the “photo export” was only a list of links.
Conversely, a folder of images does not give an importer a dependable table of dimensions, categories and identifiers. Renaming files can make a package more readable, but it should not be used as a substitute for structured metadata when the receiver needs structured metadata.
Send both when context and contents must travel together
For the product launch, the catalog manager can export a CSV containing Product Reference, Display Name and Approved Photo Count, then download the matching photos into product-reference folders. The count is a field or check the team deliberately prepares; it is not a promise that either exporter generates a reconciliation report.
Use the same approved record selection for both outputs, while separately reviewing their field selections. Agree on a stable delivery version and ask collaborators not to change the selected records during preparation. Check the result rather than assuming two downloads taken at different times are an atomic snapshot.
Compare every expected product reference with the package, investigate missing files and inspect a sample of the actual images. If a product has several photos, define whether the CSV represents the product or individual photos. A row count and a file count need not match, but the relationship should be explainable.
Choose between a fresh endpoint and a fixed delivery
Freshness depends on the chosen mode. The CSV Exporter mode guide distinguishes real-time exports within a record limit from complete exports serving the most recently generated cached file. Refresh a cached snapshot with Generate Now when needed, and inspect the downloaded result. Do not assume every reusable URL immediately reflects a just-edited record. A fresh retrieval also differs from a fixed delivery whose contents both sides already reviewed.
For an agreed one-time handoff, retain the inspected CSV and ZIP as that delivery version. Record the preparation date and selection reference in your normal delivery notes. If the source changes afterward, decide whether to issue a new version rather than silently treating an earlier package as current.
Treat generated download URLs as access paths and share them only through the intended process. Bulk download links support password protection, but a password does not establish that the selected fields and records are appropriate for the audience. Review contents before sharing.
Make the smallest handoff that meets the job
Use CSV alone for a tabular review or import that does not require local file copies. Use an attachment archive alone when the recipient already has the necessary context and needs only the files. Use both when they need to associate reusable files with structured record values.
Check the current plan and volume limits before committing to a large export. Smaller filtered batches can be easier to inspect and transfer. Keep the source base and its relationships under the organization’s normal backup and retention process; neither a CSV nor an attachment ZIP recreates the complete working system.
A successful handoff is one the recipient can use: the expected records, the expected files and an unambiguous way to connect them. Choose the format around that outcome.


