Every upload ready to play, and the files stay yours.
Most of your users film on phones that record HDR by default, and on standard screens those uploads often look washed out. silken processes every upload, whatever was sent, turns phone HDR into a standard version your team tunes, and writes the result into your own storage.
A free test on your own files · or book a meeting
What changes for your business.
Uploads that look right
Phone HDR comes out as a standard version your team tunes, so users stop complaining about washed-out video and support stops guessing why.
When it matters Users complaining about how their videos look.
Nothing for your engineers to babysit
Every upload is processed, whatever was sent, and every job finishes or reports clearly why not, with automatic retries.
When it matters A growing upload volume; conversion failures costing support time.
Your files stay yours
Uploads and results stay in your own storage, so your archive and your delivery choice stay yours too.
When it matters A storage or delivery move; files that must stay in your custody.
Nothing to replace.
- User upload
- your storage
- silken
- your storage
- your feed and player
Your upload flow, feed and player stay yours. Your backend submits a job per upload and hears back from a signed webhook when the versions are written.
Four steps from upload to playable.
- 01The upload lands in your bucket
Your app keeps its own upload path: direct-to-bucket, resumable, whatever you run today.
- 02Your backend submits a job
Signed source and destination URLs, the profile for this kind of upload and an Idempotency-Key, so a retried request never makes a second job.
- 03silken writes the renditions back
Playable renditions in your bucket, under the prefix you chose.
- 04A signed webhook says it is done
Verify the HMAC signature, mark the post playable, and your feed shows it.
{
"job_id": "job_8f2c…",
"status": "completed",
"profile": "sdr_1080p",
"billable_minutes": 0.42,
"output_bytes": 41829311,
"timestamp": 1790830000
}Signed with HMAC-SHA256 over the timestamp and the raw body. Webhook reference
HDR from phones, SDR for everyone else.
Phones record HDR by default, and the two families use different transfer functions. silken detects HDR10 and HLG per upload and tone-maps to SDR for screens that need it, with the settings you choose, so one family does not come out wrong.
“Some devices were creating HDR videos with the PQ transfer function, while others used HLG … tone-mapped videos may be too bright or too dark.”
Billed for what each clip delivered.
- Measured
- Source and output durations are measured per job and charged at the published per-minute rates, rounded up to a microdollar.
- Per rendition
- Each rendition you ask for is its own line, so a 720p-only clip costs less than a full ladder.
- Free each month
- 1,000 output minutes each calendar month, for standard SDR H.264 outputs up to 30 fps, cover your first uploads.
- At volume
- Committed volume and enterprise terms are agreed with sales.
- Preview images
- Choose poster frames and thumbnail galleries, with sprite sheets for player scrubbing. Included with Standard and Fast jobs.
Questions
How does silken fit an upload flow?
Your app stores the upload in your bucket, submits a job with signed URLs and an Idempotency-Key, and receives an HMAC-signed webhook when the renditions are written back.
What happens with HDR phone uploads?
HDR10 and HLG uploads are detected and tone-mapped to SDR for screens that need it, with controls you can tune per job.
How are short clips billed?
By the measured duration of each delivered rendition, in microdollars, at the published rates. There is no input fee.
Send us your hardest files.
Send us 50-100 real uploads: staff phones are fine, plus the files users complained about and an old-format file. We agree the results date after engineering confirms capacity. You see the share of HDR, the time to playable, the failures, the picture on your own devices and the monthly bill at your views per upload. Free within the standard scope.