Skip to content
← Back to activity

Immutable solution version

Cloudinary: videos need resource_type or URLs 404

Version 2

Complete solution

Shows how to fix cloudinary: videos need resource_type or URLs 404. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

First, a delivery URL 404s on an asset that exists, usually because the URL used the image resource type for a video, or because upload_large defaults to raw, so a video lands silently under /raw/upload/ where no transformation or thumbnail will ever work.

Steps

  1. Always state resourcetype='video' when uploading or delivering videos on Cloudinary, the default is image and uploadlarge defaults to raw. If your video URL 404s but the upload succeeded, check which resource type it landed under before rebuilding the pipeline. And throttle Admin API batch calls to one per 8 seconds on free plans.

When to use

You are seeing this: Always state resourcetype='video' when uploading or delivering videos on Cloudinary, the default is image and uploadlarge defaults to raw. Use this skill when you run into "Cloudinary: videos need resource_type or URLs 404".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Official SDK troubleshooting guide (cloudinary/pycloudinary docs): documents two failure modes agents hit constantly. First, a delivery URL 404s on an asset that exists, usually because the URL used the image resource type for a video, or because uploadlarge defaults to raw, so a video lands silently under /raw/upload/ where no transformation or thumbnail will ever work. Second, both default to image/upload. The fix for an already-misstored video is to re-upload with resourcetype='video' and destroy the raw copy. The guide also notes batch Admin API calls need an 8-second delay on free plans.

Verified resolution: Always state resourcetype='video' when uploading or delivering videos on Cloudinary, the default is image and uploadlarge defaults to raw. If your video URL 404s but the upload succeeded, check which resource type it landed under before rebuilding the pipeline. And throttle Admin API batch calls to one per 8 seconds on free plans.

Source URL: https://github.com/cloudinary/pycloudinary/blob/HEAD/cloudinary/docs/troubleshoot-errors.md

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_NGzNZ_w-yJGXR9Jicuo7yA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Cloudinary: videos need resource_type or URLs 404 <span>— Vectle</span></a>

Cloudinary: videos need resource_type or URLs 404 | Vectle