Faqs

Video Uploads and Processing

DynTube supports several upload paths so you can add a video manually or integrate ingestion into your application. Every path should end with the same operational checks: the complete source reaches DynTube, processing finishes, and the published output plays with the intended project settings.

Which upload method should I use?

  • Dashboard upload for an operator adding individual files.
  • Remote URL ingestion when DynTube can fetch a stable source URL.
  • Server API multipart upload for trusted backend integrations.
  • Signed browser upload sessions when a web client needs to upload without receiving your secret API credentials.

Keep API keys and signing credentials on a trusted server. For browser uploads, request a narrowly scoped signed session from your backend. For remote ingestion, keep the source reachable for the full transfer and avoid URLs that expire before DynTube can fetch the object.

What happens after transfer?

Upload completion means the source transfer finished; it does not necessarily mean the video is ready for viewers. DynTube processes the source into the outputs configured for the project. Duration, resolution, codec, output ladder, and queue demand affect the time required. Follow the asset's processing state and wait for successful publication before distributing its playback URL.

Which files work best?

Use a complete, clean source with a stable frame rate, correct aspect ratio, and audio that matches your intended audience. A broadly compatible MP4 is a practical choice. Avoid uploading a repeatedly compressed download when the original master is available, because processing cannot restore detail already removed from the source.

How do storage and processing allowances apply?

The current plan catalogue and account usage determine available storage, processing, and related entitlements. Stored-library size and recently processed input are different measures. Removing a published asset begins the deletion workflow, but it does not imply that every rolling processing allowance resets immediately.

Before a bulk migration, check current usage and estimate both source input and processed output. Upload in controlled batches, verify results, and leave enough capacity to retry failed sources. If your workflow constantly replaces a large library, ask support to validate the plan rather than relying on a monthly-limit example from an older document.

What should I do when an upload fails?

  1. Record the video or upload identifier and the exact error.
  2. Confirm the source is complete, readable, and within current account allowances.
  3. For URL ingestion, verify the URL is reachable without an expired session or blocked requester.
  4. For API upload, verify authentication, request format, size, and retry behavior.
  5. Retry only after identifying whether the failure happened during transfer or processing.

How can I avoid duplicate uploads?

Give each source a stable identifier in your integration and persist the DynTube result before retrying. After an uncertain network response, query the upload or video state before sending the same large file again. This reduces duplicate processing and makes bulk migrations easier to reconcile.

  • HLS Streaming & Storage
  • Bandwidth
  • Video Options

Something missing or wrong here? Tell us and we will correct it. New to DynTube? Start with uploading and embedding.