Remove Invisible Watermarks from AI-Generated VideosThe Video Remix API helps you remove invisible watermarks that AI video generation platforms add to their content. By processing your videos through our API, you can ensure clean, watermark-free output for your use cases.
Introduction
The Video Remix API allows you to process video files by providing a URL to the video. The API downloads the video from the provided URL, applies your specified transformations, and processes it to remove invisible watermarks.Upload Your Video FirstBefore using the Remix API, you need to upload your video file to cloud storage such as Cloudflare R2 or AWS S3 and make it publicly accessible. The API requires a direct URL to your video file.
Authentication
All requests to the Remix API require authentication using an API key passed in thex-ty-api-key header.
Endpoint
How to Upload Your Video
Before using the Remix API, you need to upload your video to cloud storage. Here are the recommended options:Option 1: Cloudflare R2 Storage
Cloudflare R2 offers S3-compatible storage with no egress fees.- Create an R2 bucket in your Cloudflare dashboard
- Upload your video file to the bucket
- Make the bucket or object publicly accessible
- Use the public URL in your API request
https://pub-abc123.r2.dev/my-video.mp4
Option 2: AWS S3 Storage
AWS S3 is a widely-used object storage service.- Create an S3 bucket in your AWS console
- Upload your video file to the bucket
- Configure the bucket policy or object ACL to allow public read access
- Use the public URL in your API request
https://my-bucket.s3.amazonaws.com/my-video.mp4
Other Storage Options
Any cloud storage service that provides publicly accessible URLs will work, including:- Google Cloud Storage
- Azure Blob Storage
- DigitalOcean Spaces
- Backblaze B2
Request Format
The API accepts JSON with the following fields:| Field | Type | Required | Description |
|---|---|---|---|
video_url | String | Yes | URL to the video file (must be publicly accessible) |
parameters | Object | No | Optional processing parameters |
Processing Parameters
Theparameters field accepts an object with optional processing parameters. All parameters are optional and will use default values if not specified.
| Parameter | Type | Default | Range/Values | Description |
|---|---|---|---|---|
zoomFactor | number | 1.0 | 0.1 - 5.0 | Zoom level for the video |
hue | number | 0.0 | -180 to 180 | Hue adjustment in degrees |
playbackSpeed | number | 1.0 | 0.1 - 5.0 | Video playback speed multiplier |
saturation | number | 1.0 | 0.0 - 3.0 | Color saturation multiplier |
brightness | number | 0.0 | -1.0 to 1.0 | Brightness adjustment |
contrast | number | 1.0 | 0.0 - 3.0 | Contrast multiplier |
volume | number | 1.0 | 0.0 - 2.0 | Audio volume multiplier |
removeAudio | boolean | false | true/false | Whether to remove audio from the video |
algorithmFingerprint | string | ”Fingerprint” | Any string | Algorithm identifier for processing |
hueShift | number | 0.0 | -180 to 180 | Additional hue shift in degrees |
gamma | number | 1.0 | 0.1 - 3.0 | Gamma correction value |
temperature | number | 1.0 | 0.5 - 2.0 | Color temperature adjustment |
noise | number | 0.0 | 0.0 - 1.0 | Amount of noise to add |
sharpness | number | 1.0 | 0.0 - 3.0 | Sharpness multiplier |
blend | number | 0.0 | 0.0 - 1.0 | Blending amount |
bilateVariation | number | 1.0 | 0.0 - 2.0 | Bilateral filter variation |
frameBlending | number | 0.0 | 0.0 - 1.0 | Amount of frame blending |
timeShift | number | 0.0 | -10.0 to 10.0 | Time shift in seconds |
Example with Multiple Parameters
Response Format
Success Response (200 OK)
Error Responses
- 400 Bad Request: Invalid video URL or parameters
- 401 Unauthorized: Invalid or missing API key
- 413 Payload Too Large: Video file exceeds size limit
- 429 Too Many Requests: Rate limit exceeded
Code Examples
React Example (Complete Component)
Video URL Requirements
Your video must be uploaded to cloud storage (Cloudflare R2, AWS S3, etc.) before processing. The URL must meet these requirements:- Publicly Accessible: The video URL must be publicly accessible (no authentication required)
- Cloud Storage: Must be hosted on Cloudflare R2, AWS S3, or similar cloud storage
- Supported Formats: MP4, MOV, AVI, WebM
- Max File Size: 150MB
- Direct Links: URL must point directly to the video file (not a webpage)
Error Handling
400 Bad Request
401 Unauthorized
429 Too Many Requests
413 File Too Large
Retry Logic Example
Best Practices
- Valid URLs: Ensure video URLs are publicly accessible and point directly to video files
- File Size: Keep video files under 150MB for optimal processing
- File Formats: Use supported formats (MP4, MOV, AVI, WebM)
- Error Handling: Always implement proper error handling for network and API errors
- Rate Limits: Be mindful of rate limits and implement retry logic with exponential backoff
- API Keys: Keep your API keys secure and never commit them to version control
