Batch uploads and folder structure

For a handful of files, the in-page uploader is the fastest path. For dozens or hundreds, the techniques below save real time.

Drag-and-drop a folder

Both Chrome-based browsers and Safari support folder drag-and-drop. On the Uploads → Upload page, drag an entire folder into the upload area and Vulgate will:

Walk the folder tree recursively.
Queue every supported file for upload (skipping unsupported types like .zip).

If you need to group documents inside Vulgate later, use Collections; a Collection can group documents however you like without duplicating them.

Uploading from cloud storage

The upload picker on the Upload page lets you bring files in from:

Google Drive — pick individual files or whole folders. Vulgate stores its own copy; nothing is left in your Drive.
Dropbox — same flow as Drive.
URL — paste a direct link to a publicly accessible PDF, image, or audio file and Vulgate will fetch and ingest it.

Connected-source uploads count against the same ingest quota as files from your local disk.

Uploading via the API

For programmatic or really large batches, use the Vulgate Ingest API. The flow is:

GET /api/uploads to request a signed upload URL for a single file.
PUT your file to the signed URL with the headers returned in step 1 (no auth needed; the signature does the work).
POST /api/jobs with the file ID returned in step 1 to start ingestion.

Full reference:

Recommended limits

Per file: see Uploading documents — an overview for the current size cap.
Concurrency: Vulgate parallelizes file transfers automatically.

What to do after the batch finishes

Spot-check a handful of documents in Library to make sure OCR and structuring look correct.
Group related documents into Collections for easier search filtering.
Bookmark documents you'll reference often — see Bookmarks.