What is a public CDN URL?
A public CDN URL is a fetchable HTTPS URL served through a content delivery network so external systems can retrieve file bytes reliably.
A public CDN URL is a delivery endpoint, not a collaboration page.
The destination system should receive file bytes with the headers it expects. That is different from a share link, preview route, or app attachment page.
HTTPS access
External APIs can fetch the URL without your account session.
Stable headers
Content type and size help OCR, AI, social, document, and webhook systems process the file.
Edge delivery
CDN delivery reduces the chance that a slow origin or app page breaks a fetch.
CDN URLs are useful when files are inputs to other systems.
A workflow might generate a PDF, image, screenshot, export, or document that another system can only fetch by URL.
AI and OCR
Model and extraction APIs often ask for a public URL they can fetch asynchronously.
Social publishing
Publishing APIs need image or media URLs that remain reachable until the platform has fetched the asset.
CRM and support
Automation tools can attach files by passing a direct URL into the destination API.
Public does not have to mean permanent.
Public workflow files should have an end state through expiry, deletion, or account retention policy.
Set expiry
Use retention windows that survive queue delays but do not leave files public forever.
Delete after fetch
Use `file_id` to remove public access after the destination confirms processing.
Keep customer files out of search
Uploaded files should not be treated as indexable product content.
Answers before the workflow breaks
Is a public CDN URL safe for sensitive files?
Use short expiry, delete after processing, and avoid broad sensitive document use until account policy controls match the risk.
Can a public CDN URL expire?
Yes. A file URL service can expose an expiry window and remove access after the workflow no longer needs the file.
Do public CDN URLs get indexed by Google?
Marketing pages should be indexable, but customer-uploaded file URLs should not be treated as search content by default.