Live P2

Check file and parser limits

Use the current admission formats and technical ceilings without treating code limits as service guarantees.

Availability
Live
Last verified
Runtime anchor
ab084f79c5ed3fc6a28f07c64b29920944a0e5db
Certification anchor
db23559179dc3c67be8a1ab16a0f07323b9820f7
Evidence note
Admission and parser constants were read from the audited runtime. Production infrastructure can impose lower limits and was not stress-tested to every ceiling for documentation.

What this does

Use the current admission formats and technical ceilings without treating code limits as service guarantees.

Before you begin

  • Check storage/provider limits in addition to ArtDrop admission limits.
  • Start with one file when testing a new size, parser, or provider route.

What changes outside ArtDrop

Reading this reference is read-only. Uploading admitted files can stage, analyze, store, and publish them according to the chosen flow.

Steps

  1. Artwork

    Use .tif, .tiff, .png, .jpg, or .jpeg. One upload admits up to 50 file parts. The code-level artwork/request ceiling can reach 2 GiB, but CDN, proxy, browser, memory, storage, and provider limits may fail earlier; it is not a 2 GiB service promise.

  2. Sheets and sidecars

    Use .csv or .xlsx sheets, up to four per upload and 2 MiB each. Use per-image .json sidecars up to 2 MiB. A sidecar overrides conflicting sheet values.

  3. Filenames

    Keep admitted filenames at or below 180 characters, basename-only, non-hidden, and limited to safe letters, numbers, periods, underscores, and hyphens where the batch parser applies.

  4. Voice sources

    Voice Trainer accepts DOCX, PDF, TXT, CSV, JPG, JPEG, and PNG: up to 10 files, 25 MiB each, 32 MiB combined, and PDFs up to 50 pages. OCR is stricter in practice.

  5. Storage-specific limits

    Dropbox does not provide the current path with chunked uploads above 150 MB. Large Drive files can trigger a virus-scan interstitial around 100 MB that a provider cannot cross. Prefer B2 or public R2 for large print files.

Expected result

The parser accepts a well-formed test input and reports a specific admission error rather than silently changing destinations or fields.

Limits and non-goals

  • Implementation ceilings can change and should not be used as performance or uptime commitments.
  • Provider product dimensions and DPI requirements are separate from upload byte limits.

Troubleshooting

  • On 413/timeout/memory errors, reduce file count/size or use an external storage route; do not repeatedly submit a giant batch.
  • On parser error, isolate one artwork plus its one sheet/sidecar and correct the exact reported field.

How to undo or clean up

Remove rejected local inputs or correct them before a new upload. If an accepted flow already published, clean external records separately.