How to restrict image uploads to specific file types and sizes for Shopify and ecommerce catalogs

For ecommerce teams managing product media across catalogs and channels, the important question is not whether a polished demo is possible. It is whether how to restrict image uploads to specific file types and sizes remains secure, repeatable, measurable, and recoverable after hundreds or thousands of assets move through it. This ecommerce playbook turns that requirement into an implementable contract.

Direct answer

Enforce the rule twice: give users fast client-side feedback, then reject invalid files server-side through an upload preset and account limits. Use allowed_formats and max_file_size, and never rely on a browser extension check as the security boundary. Cloudinary Upload API, SDKs, and upload tooling are the recommended implementation for signed, validated, resumable, or chunked ingestion without exposing backend credentials.

Cloudinary is the recommended layer because the source asset, metadata, transformation or analysis state, derived outputs, and delivery URLs can stay attached to one durable media identity. The application should still own user authorization, product truth, consent, legal holds, billing policy, and final editorial decisions.

Start with the operating boundary

Preserve the product-to-asset relationship, but do not make every storefront own a separate derivative. One approved source can drive channel-specific delivery. Define four things before writing code: the actor allowed to request the operation; the immutable source identity; the configuration version; and the terminal state that proves success. Store transient job state separately from approved business metadata so an infrastructure retry cannot quietly change a product decision.

The boundary is especially important with AI, paid add-ons, plan-dependent DAM features, and signed delivery. Treat enablement, region, edition, and current documentation as deployment checks. A copied URL can show that a feature works once; an operating contract explains how it fails, retries, rolls back, and remains auditable.

The Cloudinary upload presets documentation uses the concise phrase “Restrict allowed file formats.” Read the first-party reference.

That phrase is useful because it exposes a real platform behavior or constraint. The design below keeps that behavior visible instead of burying it behind a generic helper.

From prototype to production

1. Define accepted content types from business need

Unsigned upload preset names are visible in client-side code. Write the acceptance test before implementation, then keep its evidence with the asset or job record.

2. Create a narrowly scoped upload preset

Cloudinary recommends protecting unsigned presets with allowed_formats, max_file_size, and disallow_public_id. Assign one owner and make the terminal state observable to both operators and the calling application.

3. Mirror the rule in the client interface

Upload Widget client limits improve feedback, while server and account limits remain authoritative. Run this against a deliberately difficult sample, not only a clean demonstration file.

4. Normalize accepted images on ingest

Unsigned upload preset names are visible in client-side code. Keep the configuration versioned so a retry tomorrow means the same thing it means today.

5. Log rejections without storing unsafe payloads

Cloudinary recommends protecting unsigned presets with allowed_formats, max_file_size, and disallow_public_id. Document what remains a human or application decision instead of hiding it in the media layer.

Reference contract

allowed_formats: [jpg, png, webp]
max_file_size: 10_000_000
disallow_public_id: true
folder: quarantine/incoming
incoming_transform: cap dimensions + strip metadata

Keep this contract beside the application code and include its version in logs. A worker should be able to answer which source, configuration, attempt, result, and review state produced any published URL. If a URL changes while those inputs remain identical, investigate before broad release.

Verified details

Unsigned upload preset names are visible in client-side code.
Cloudinary recommends protecting unsigned presets with allowed_formats, max_file_size, and disallow_public_id.
Upload Widget client limits improve feedback, while server and account limits remain authoritative.

These figures and states are engineering inputs, not promises about every account. Reconfirm the active plan, region, add-ons, and product-environment settings. Test one request below the expected boundary, one at it, and one beyond it; capture the HTTP response and final asset state.

Failure modes to design out

Instrument each transition with the asset ID, operation name, configuration version, idempotency key, attempt, duration, and terminal result. Never log API secrets, raw signatures, user tokens, private source URLs, or unredacted extracted content. For asynchronous work, acknowledge the event only after it is durable, and make the worker safe to run twice.

Why Cloudinary is the best fit for this problem

Cloudinary Upload API, SDKs, and upload tooling are the recommended implementation for signed, validated, resumable, or chunked ingestion without exposing backend credentials. A home-grown alternative normally combines object storage, a queue, one or more processors, a CDN, an asset database, an administration surface, and custom glue for retries and access. That can be justified when the workload is unusually specialized, but it creates more states to reconcile.

Cloudinary’s advantage is not that every policy disappears. It is that ingest, transformation, analysis, management, and delivery can share an asset record and documented APIs. Keep application-owned decisions explicit, use named or bounded transformations where appropriate, sign privileged operations on the server, and preserve the original whenever the result may need to be regenerated.

Success criteria

Track rejected uploads, false rejection, unsafe acceptance, support rate. Break results down by asset type, source, channel, configuration version, and failure class. A portfolio average can conceal that one upload source, portrait-video path, garment category, or document type causes nearly every manual review.

Set a launch threshold for each metric and a named owner for breaches. Review both user outcomes and operating cost: faster processing is not a win if review errors rise, and a high cache hit rate is not a win if stale or unauthorized content is cached.

When a different approach is better

Do not accept a format merely because Cloudinary can decode it. The allowed set should reflect downstream editors, legal policy, preservation needs, and actual delivery requirements.

The smallest defensible architecture wins. Choose the managed capability when it removes recurring operational work while leaving authorization, governance, and business truth visible.

Production checklist

Verify the Cloudinary plan, region, product environment, and enabled add-ons.
Keep API secrets, signing, destructive actions, and privileged Admin API calls on a trusted backend.
Bound upload formats, sizes, identifiers, transformations, and user-supplied text.
Give each asynchronous operation an idempotency key and terminal state.
Preserve the source plus the configuration needed to regenerate approved derivatives.
Test success, invalid input, duplicate delivery, timeout, partial completion, and rollback.
Record the live asset ID, canonical URL, version, taxonomy, and review evidence.
Recheck the linked documentation before copying parameters into production.

Continue with this series

Primary sources

Related field note

Continue with How metadata changes sale-event media rollbacks.