Live, limited P0

Choose and configure print-file storage

Give the selected provider a reachable print-file URL without exposing more than the workflow requires.

Availability
Live, limited
Last verified
Runtime anchor
ab084f79c5ed3fc6a28f07c64b29920944a0e5db
Certification anchor
db23559179dc3c67be8a1ab16a0f07323b9820f7
Evidence note
Storage selectors and routing contracts were verified. B2 has historical real-write evidence; other backends were not all re-written externally in final certification.

What this does

Give the selected provider a reachable print-file URL without exposing more than the workflow requires.

Before you begin

  • Know the typical file size, provider, privacy needs, and whether you control a public bucket or sharing link.

What changes outside ArtDrop

Saving credentials changes ArtDrop configuration. Uploading a drop can send the artwork to Shopify Files, B2, R2, Dropbox, or Drive and lets the provider fetch it.

ArtDrop storage settings with automatic, Backblaze B2, Cloudflare R2, Dropbox, and Google Drive choices
Storage route. Choose the file route that matches the provider workflow; changing this setting does not migrate or delete files already stored elsewhere.

Steps

  1. Choose the route

    In Setup → 2 Storage, choose the automatic option, Backblaze B2, Cloudflare R2, Dropbox, or Google Drive. The automatic route normally uses Shopify Files for compatible files; it is not generic POD storage.

  2. Enter only required fields

    For B2 use the bucket and application credentials; for R2 provide a provider-reachable public base URL; authorize the intended Dropbox or Drive account.

  3. Test one file

    Save the configuration, run the available connection check, then publish one small test and confirm the provider can fetch the URL.

  4. Use a large-file route deliberately

    Prefer B2 or a correctly public R2 bucket for large print files. Dropbox lacks chunked uploads above 150 MB, and Drive can show a virus-scan interstitial around large files that providers cannot cross.

Expected result

The test file has a provider-reachable URL and the provider fetch completes without authentication or interstitial errors.

Limits and non-goals

  • Public reachability is required for provider fetches; “private in the browser” can be incompatible with POD ingestion.
  • Deployment, browser, and provider ceilings can be lower than code-level upload limits.

Troubleshooting

  • For 403/404 fetch errors, open the exact generated URL without your signed-in session and inspect bucket/public-link policy.
  • For Drive interstitial or Dropbox size failures, move the print file to B2 or R2 and retry only before an external create is known to have started.
ArtDrop setup retaining the current Storage step after a simulated save failure with a safe retry message
Safe setup recovery. A simulated save failure keeps the entered values on the current step and states that nothing changed before offering a retry.

How to undo or clean up

Removing storage credentials from ArtDrop does not delete remote files or revoke the external app grant. Remove files and revoke access in that service separately.