Part one solves the problem that stops most bulk imports before they start: Drupal will not attach a picture it has no record of. Copying two hundred files into the files directory does nothing on its own — the database has no file entity for any of them, so an import that names them fails row after row.
Getting the files onto the server
Any route works, and the video shows two. A file manager such as IMCE gives editors a browser-based upload; SFTP or a shell copy suits a large batch better. PB Import itself does not depend on IMCE — its .info.yml lists only core modules plus Paragraphs and Entity Reference Revisions — so pick whichever tool you already trust and put everything in one folder inside the public files directory.
Registering what you uploaded
The registration form lives at /admin/content/paragraphs/register-uploaded-files, also reachable under PB Import in the Content menu. It asks a single question, Image Folder Relative Path, and it wants the path relative to the files directory — gallery/austin, not a full server path. Submit it and every picture in that folder becomes a managed file the importer can find by name.
Preparing the pictures before you upload
- Use jpg, jpeg, png, gif or webp — those are the formats the importer accepts.
- Give each file a short, lowercase, stable name; the CSV matches on exact file name, and matching is case sensitive.
- Resize before uploading. Drupal will generate derivatives, but it will not rescue a 6000px original that slows every editor preview.
- Keep one folder per batch, which makes the relative path easy to type and easy to re-run.
What to do next
PB Import 2.x targets ^11.3 || ^12 and expects Paragraphs Bundles 2.x alongside it. Confirm the requirements on the Paragraphs Bundles Import module page, then continue to part two, where the spreadsheet that names these files gets built column by column.
Would rather have this configured for you? That is Drupal development — or get in touch.
