From quick clips to full courses.
Keep public video files in your library and use the built-in player or your own compatible HTML5 player.
VIDEO & AUDIO STORAGE
Your player.
Your website.
Our media storage.
Store long recordings and publish them through a direct link or an embed. Keep the rest of your publishing stack exactly where it is.
Podcasts, music, and recordings.
Audio gets the same storage, direct linking, share-page, and embed workflow.
Keep the download available.
Use a direct content address when someone needs the source recording or a supporting file.
PREPARE ONCE. PUBLISH WHEREVER.
A video file made for the web.
Storage and encoding are different jobs. PinThis serves the file you upload; it does not run a cloud transcoding pipeline or generate adaptive quality variants for you.
For common browser playback, prepare MP4 with H.264 video and AAC audio. Placing the MP4 index at the front helps the player read its metadata early. A tail index may require an extra range request and delay startup. Keep your original master separately if you need it.
If your video already uses compatible codecs, moving its index may be enough. Encoding a different codec requires a conversion. The account’s media checks explain common issues.
Three ways to share your media.
| Use | Choose |
|---|---|
| A simple share link | The media’s watch page |
| A player inside your website | The supplied iframe embed |
| Your existing player or download button | The direct media URL |
Watch pages expose OpenGraph and oEmbed metadata for supported media. Copy the exact URL and embed code from your account; media paths inside folders stay part of that address.
What fast delivery depends on.
HTTP range support lets a compatible player request a portion of the media file. Memory and disk caches help repeated requests avoid another storage read. Recently published file headers receive limited, temporary cache priority to help with startup. This shares the existing cache space and has a separate limit on background reads. Older recordings and new seek positions may still require retrieval from storage.
That makes your format, bitrate, viewing pattern, and busiest publishing window useful planning inputs. PinThis does not promise that every video or every part of every recording will always be cached.
Plan for bytes delivered.
Storage is the size of your library. Delivery is the data sent to viewers, including repeated and cached views. Publish includes 3 TB of delivery per UTC calendar month, with $2 per additional TB. These are decimal TB. Additional delivery requires opt-in and a monthly spending limit. The previous month’s actual additional delivery is added to your next monthly bill; outstanding usage is settled when your subscription ends.
One media library.
Many places to publish.
Start with one representative recording and check its playback on your site.