Normal

small_cedric.webp

thumbnail_cedric.webp

cedric.webp

Cédric Montet

large_api-video-blog-product-updates.png

medium_api-video-blog-product-updates.png

small_api-video-blog-product-updates.png

thumbnail_api-video-blog-product-updates.png

api-video-blog-product-updates.png

Product updates

Having the right tools to monitor external systems can make or break your ability to provide a smooth experience for your users. At api.video, we know these tools can go a long way in helping you more easily troubleshoot user issues from day one.

&nbsp;

Today, we’re excited to introduce audit logs, to give you even more visibility into your integration!

## Event logs in the Dashboard

The first step to troubleshooting an issue is being able to look under the hood.
Starting today, you can view your most recent API request events directly in the Dashboard. To view your API request events, follow the steps below. 

1. Head over to the new event [logs page in the Dashboard](https://dashboard.api.video/audit-logs).

large_Screenshot 2024-03-12 at 10.11.46.png

medium_Screenshot 2024-03-12 at 10.11.46.png

small_Screenshot 2024-03-12 at 10.11.46.png

thumbnail_Screenshot 2024-03-12 at 10.11.46.png

Dashboard-audit-logs.png

2. Choose how you want to view the events by setting filters based on method, time window, or status.

large_Screenshot 2024-03-12 at 10.12.45.png

medium_Screenshot 2024-03-12 at 10.12.45.png

small_Screenshot 2024-03-12 at 10.12.45.png

thumbnail_Screenshot 2024-03-12 at 10.12.45.png

dashboard-audit-logs-filters.png

## Audit logs period retention

Note that we offer different period retention based on your environment:

&nbsp;

- Sandbox: 1 day
- Production, pay as you go: 5 days
- Enterprise: 60 days

&nbsp;

We’ll continue to invest in features that make it easy and efficient for you to build on api.video.

&nbsp;

In the meantime, we welcome any feedback on these latest improvements and anything else you may want to see! Reach out to us via the [Community](https://community.api.video/) or the chat box.

Audit Logs on api.video Dashboard

large_AuditLogs.webp

medium_AuditLogs.webp

small_AuditLogs.webp

thumbnail_AuditLogs.webp

AuditLogs.webp

Easier troubleshooting with audit logs

small_alexw.png

thumbnail_alexw.png

alexw.png

5a22d420c9a5a7-416105621512231968826.png

linkedin Alex W

Alexandre Willot

Getting the best quality of videos without worrying about cost hikes and compliance issues that come with storing those videos is not easy. We at api.video understand that. 

&nbsp;

So, in response to your needs and in our ongoing effort to improve your experience, we're proud to introduce a new video storage option in the United States of America (USA). This expansion complements our existing services in the European Union (EU) and offers you even greater flexibility in choosing the optimal storage location for your videos. 

&nbsp;

_(If decoding text feels like a secret mission for your eyes, switch gears and dive into the video.)_





## What does this update mean for you?
With this upgrade in our infrastructure, you decide where you want your videos to be stored – in the USA or in the EU. This translates to: 

### 1) More control over your video storage location to comply with laws

Select the storage location that best suits your needs, whether for compliance with local laws or based on personal or customer preference. This will ensure that your video content adheres to all relevant legal standards for you or your customers. 

### 2) Diversification of your user base with multi-region storage

If you are working on a project in Europe and one project in the US, you can benefit from multi-region storage. Each project you create in your account will have a unique API key and its own distinct settings, including the video storage location. This means that you can link each project to a single region based on your customer's video storage preferences.

### 3) Faster video playback

On top of the new storage in the US, we have opened new delivery servers in North America, and improved our CDN services in the region. Both initiatives now guarantee faster, more efficient video delivery within North America. This means that your American users will experience faster and higher quality video playback than ever before.

&nbsp;

In addition to this flexibility of choosing your storage location, api.video also offers improved video performance, [reduced costs](https://api.video/blog/product-updates/video-encoding-pricing-update/), [greener carbon footprint](https://api.video/blog/company/asics-based-video-encoding/) and enhanced [flexibility ](https://api.video/blog/product-updates/white-labeling-api-video/)for expanding your video functions. These advantages stem from our complete ownership of the video infrastructure.

## Conclusion
In a nutshell, this expansion of our video storage and delivery capabilities is a step towards better serving your video infrastructure needs, locally and globally. We're grateful for your trust, and we can't wait to see what you'll create.

&nbsp;
 
 
_To start using api.video and see how this works, [sign-up](https://dashboard.api.video/register) for a free sandbox account now._


New video storage capabilities in the US: Introducing multi-region video hosting

small_multi_region_A.png

thumbnail_multi_region_A.png

multi_region_A.png

video api

Video stream

Neda.jpg

Neda Ashrafi Amiri

2022 is coming to an end, but for us, it’s just the beginning of a new era 🦋

It has been a year full of innovations and growth for the api.video team. We did everything to make video streaming simpler and easier than ever before! Adding videos to your products is our mission and our everyday mantra 🧘‍♀️

In this article, we would like to celebrate 🎉 and look back on some of the major highlights of 2022 together 🥂 

## **All-in-one infrastructure 🎈**

We built an infrastructure that is strong and independent. api.video offers an all-in-one dedicated encoding machines and CDN setup. We have observed 100% availability of our services this year, with no downtimes. What does this mean for you? We ensure that you have stability and control over all your videos. We also monitor and track important data to improve performance and provide a flawless playback experience for your viewers.

## **Ecosystem designed for you** 🔌

You 🫵 yes you. You were our main focus this year! And you will always be our main focus. Whether you are a content enthusiast looking to add videos to your Content Management System (CMS), or a developer wanting to skip the hassles of developing applications for multiple operating systems, we created the right tools for you.

We have a growing ecosystem with many new plugins, clients, libraries, and other no-code tools. Now you can easily add videos to your favorite applications with just a few clicks!

Here is a list of some of the tools we designed for you this year 🧩

- [Plugin for WordPress](https://api.video/blog/product-updates/wordpress-plugin/)  - A plugin to embed and manage your videos into your WordPress website or blog.
- [iOS client](https://api.video/blog/product-updates/new-swift-api-client/) - A client that removes the iOS SDK to simplify api.video usage and deployment with advanced upload features.
- [React upload button](https://api.video/blog/tutorials/how-to-upload-a-video-with-react-and-nodejs/) - a fully customizable button in your application that you can implement in a few minutes.
- [Plugin for Strapi](https://api.video/blog/tutorials/api-video-strapi-plugin-add-videos-to-your-headless-cms/) - a powerful, easy, and secure plugin to bring video content to your websites and applications using the Strapi headless CMS.
- [Player for Flutter](https://api.video/blog/tutorials/api-video-player-for-flutter-playback-videos-on-your-apps/) - an api.video customizable player for Flutter built natively for Android, iOS, and the web.
- Players for [Android](https://api.video/blog/tutorials/how-to-add-an-api-video-player-to-your-android-application/) and [iOS](https://api.video/blog/tutorials/how-to-add-an-api-video-swift-player-to-your-ios-application/) applications- api.video players that help you include your videos in your Android or iOS applications easily and quickly.
- [Fully accessible player](https://api.video/product/player/) - with ARIA attributes present; the player is fully accessible to all screen reader users.
- [Next.js boilerplate](https://github.com/vercel/next.js/tree/canary/examples/with-apivideo) - a simple way to start implementing api.video with Next.js.

We are introducing a lot of exciting new tools in 2023 🎊  Don’t miss out! Follow us on [LinkedIn](https://www.linkedin.com/company/api-video/) and [Twitter](https://twitter.com/api_video) to receive the latest updates! 

## **New features inspired by you 🗣️**

We believe that the only way to grow is by listening to our customers! We listened, and here are some of the features that you requested ⚙️

- [Workspaces](https://api.video/blog/product-updates/workspace/) - Anyone can share their api.video dashboard with a colleague or a client. It's a great way to involve stakeholders in your projects.
- [Watermark feature](https://api.video/blog/tutorials/how-to-add-watermarks-to-your-videos/) - You can now add customized watermarks to your new or old videos
- [Clipping feature](https://api.video/blog/tutorials/how-to-create-a-video-clip/) - With the clipping feature, you can trim your video by selecting the exact duration you desire right inside the api.video dashboard. No more going back and forth and using other tools for clipping your videos!

We have been continuously improving our product with new features and updates. However, we are just getting started! Join us on our journey to becoming better, and post your [feedback](https://api.video/contact/)! 

## **New business opportunities 🌱**

We are in the video business, and the video industry is BIG! We know that there are a lot of business opportunities you can harness by using the api.video tools. Our experts worked on putting together a few demos for you to see how easy it is to create those opportunities with our tools. Here are some of the use cases designed for you 💡

- [Build a YouTube-like site with no code](https://api.video/blog/no-code/bubble-io-api-video-build-a-youtube-like-site-with-no-code/)
- [Build your own TikTok](https://api.video/blog/tutorials/rebuilding-tiktok-with-api-video/)
- [Create a Udemy-like learning platform](https://api.video/blog/tutorials/how-to-create-a-udemy-like-learning-platform/)
- [Build a Loom-like app with just a few lines of code](https://api.video/blog/tutorials/build-a-loom-like-app-with-just-a-few-lines-of-code/)

It sounds very BIG to create YouTube, but we make it so simple. Go BIG by keeping it simple and try out some of these demos for yourself. You may be the next BIG founder 🚀 It’s [free to try](https://dashboard.api.video/register)!

You can also find more use cases on our [blog](https://api.video/blog/)!

## **$12M Series A funding** 💰

We are very happy to share the news that api.video raised $12M in [Series A funding](https://api.video/blog/product-updates/we-raised-12-millions-to-let-you-join-our-video-first-world/). As I said, this is the beginning of a new era for us! An era of growth. But we don’t want to grow alone. We want to grow with you 🤝

We hope that you enjoyed reading the highlights of 2022. We, at api.video love our community and want to make sure that you know how much your support means to us. Let us know how to be better by posting your feedback and any ideas you may have on our [community forum](https://community.api.video/) 🫶 

On behalf of the [api.video](https://api.video) team we would like to wish you a happy holiday season and here is a video 🎬 we made just for you 🎄




All-in-one infrastructure & growing ecosystem

Highlights of 2022: all-in-one infrastructure & growing ecosystem

large_20dec22.png

medium_20dec22.png

small_20dec22.png

thumbnail_20dec22.png

2022-highlights-infrastructure-growing-ecosystem.png

t02cw29ka-u04jtt0jcg3-549047173ac2-512.jpeg

Artem Matinian

api-video-blog-tutorials.png

Tutorials

It’s natural that one will think about integrating videos into their project. There are so many use cases for a video that we cannot even start to count. From user-generated content like Youtube, TikTok, Instagram, and the likes, through e-learning apps, personal trainers, e-shopping, and the list goes on and on, there’s no limit to what you can do with moving images that zoom across the fiber optics as digital signals from one place to another. 

&nbsp;
 

Is there are catch, though? How easy is it to implement videos into your project, app, or website? In this article, we will look at the options, challenges, and solutions for getting video infrastructure up and running.

## The Casual Cloud Vendor ☁️

Probably, the first thought of every developer (with a mainstream line of thinking) is AWS. It comes naturally, as most of the existing infrastructure is probably set up on AWS, Azure, or the like. Who can blame you? it’s convenient, easily scalable, and…. can get quite expensive. Not only that, it might be difficult to implement as well; think about:

&nbsp;
 

- Having DevOps that specialize not only in AWS but also in the video area
- If you don’t have such a team, then you’ll need to hire people for that.
- Time-consuming setup
- High price

So-you-wanted-to-use-AWS-to-save-costs.png

Here’s the implementation list of all the different services to deploy and setup to have video-on-demand with AWS:

AWS-requirements.png

That’s not all; you’ll also have to build the client that uploads the videos yourself and plus all of the front-end. You can already understand the costs and time involved with this project. 

&nbsp;

“Alright”, you say, now what? isn’t it better to just build the whole architecture myself? what’s the point of using AWS if it’s costly, complex, and resource intensive?

##The DIY solution 🛠️

Let’s go with this simple idea. You want to create an upload button where users upload their videos to your app or website. You already have quite a few users and you know that the feature will be adopted quite quickly, right?

&nbsp;
 
The minimum requirements are:

&nbsp;
 

- Rent a server for $120/month (i.e Cloudflare, DigitalOcean and the likes) with the following available resources (vCPU: 4, 16GB of memory, 250GB HDD)
- Install a web server like Apache, Nginx
- Create a hosting logic on your server
- Find a third-party video player
- Create your application and add an upload button to allow your users to send their videos created with their last smartphone model.
- Allow the user to play their videos freshly uploaded with the video player
- Deploy your application on the server

&nbsp;
 

It does sound easier than AWS, right? why is the AWS solution so complex? why all of these services?

&nbsp;
 
You launch the service, and it seems to run smoothly for a few hours, and then you start to get some emails from customers, like:
&nbsp;
 

MichaelScott777 says:
```
💡 My playback is really choppy, and it takes forever for the video to load! why are you so slow (that’s what she said 😀)
```
TheShrute909 exclaims:

```
💡  Why is the video is so slow?!?!?!??!!?!? it takes the video 5 hours to show! help!!1
```

&nbsp;
 
Your users are calling out that the playback experience is poor. There is a lot of buffering before the video starts to play.

&nbsp;
 

So you start Googling around, and you discover that you can’t just upload the video; you need to encode it with different qualities, plus if you want to stream the videos, you also need to implement some specific protocols, and you start going down the rabbit hole: HLS, DASH, H.264, HEVC, AV1 and etc. “WHAT THE HELL IS ALL OF THIS?” you ask.

&nbsp;
 

Then you stumble upon something that seems like salvation: [FFmpeg](https://ffmpeg.org/)! a video processing “Swiss knife” you hail in victory and pound yourself on the chest. You’ve made it. After several weeks of sleepless nights and 59.7 coffee cups later, it’s installed, it’s running, and magically does the job (you don’t really understand how completely, but it works).

solution.png

Everything seems to run smoothly, but you are afraid to touch anything as you focus on your main product, and if you start messing around with the video monster again, you might sink more time into it. But then your users start to ask for more features around video:

&nbsp;
 

CryptoKing001 is asking for this feature:

```
💡 Heellooo!, how can I know how many people watched my videos? <3 <3 <3
```


You grab your head in fear, and the anxiety builds up. You can’t sink in more resources into that video thing, and that 3rd party video player I’ve used doesn’t provide analytics (!!!!). So, you decide to outsource the whole thing, although you did have a limited budget setup for this project, so you go over budget.

&nbsp;
 

The app seems to be running fine for a few weeks, and many users upload their videos daily. You check your monitors and discover that you are running out of disk space! the product is minutes from being down because of all of this video thing; eventually, it goes down, and you generate some bs message to your users about vertical scalability that they have no idea what you are talking about. Eventually, you rent more servers and add more disk space; the product is up again, but, again, you are way over budget already with that analytics stuff; now you have to pay more for space (argh!). At least you’ve evaded a disaster, but you get a new complaint:

&nbsp;
 

obee1kanobeeeeeeeeeeeee writes:
```
💡 why the videos don’t play after I upload them???? I have to wait for 5 minutes before it plays. MY VIEWERS ARE COMPLAINING!!! FIX IT!!!
```

Your head is already missing half of the hair it used to have before you started the project, and now this?! 

&nbsp;
 

You start investigating and find out that you have 100% CPU utilization on the video server; remember that magical salvation that you installed on the server: FFmpeg? now it gobbles up most of the CPU to encode the videos. So, you write another bs message to your users about encoding and some stuff you don’t even know about (and your users don’t even care), and you start sinking more money into the project. You buy more CPU and start scaling again.

&nbsp;
 
Few months past. You don’t need to buy shampoo anymore (at least that’s a good thing, you can save some money), most of your attention has shifted into scaling these wretched video servers, you are now an expert in video encoding and delivery, but you are losing users as they have no interest in your product, as all of your investment and resources went into this video project black hole.  You’ve hired more engineers that are dedicated to doing the video project, and the budget for the video project already went out of control a long time ago.

I-know-kungfu.png

You look back and think, how did I end up here? what could I have done better? would it be better to go with AWS? or maybe there are other solutions I could have considered?

## The Perfect Solution

Like with any other service, reinventing the wheel would probably lead to huge financial implications, but as we’ve seen AWS is not perfect as well. However, there are APIs that can solve this problem by providing you with a scalable and easy-to-use service, like api.video.

&nbsp;
 

- With api.video creating an upload scenario and even more is a matter of minutes.
- api.video has a far lower cost than AWS (check the cost calculator [here](https://api.video/pricing/aws/)) or DIY
- api.video has a strong infrastructure that is scalable and reliable
- api.video gives you the ability to select the storage location of yoru videos in the US or in the EU. This will ensure that your video content adheres to all relevant legal standards for you or your customers. 

&nbsp;
 

Check out the [get started guide](https://docs.api.video/vod/get-started-in-5-minutes) to get started in 5 minutes or create a [sandbox account ](https://dashboard.api.video/login) for free to explore api.video on your own!

Should I build my video infrastructure from scratch?

small_Frame 427319210.jpg

thumbnail_Frame 427319210.jpg

Frame 427319210.jpg

Should I build my video infrastructure from scratch? Challenge accepted

captions

screen-shot-2021-01-26-at-11-48-47-am.jpg

Erikka Innes

Captions increase your video's audience. Viewers spend more time watching captioned videos, many people watch videos with the sound off, and you can draw viewers who don't speak the spoken language of your video if you include subtitles. See ["Why You Should Caption Your Videos, Whether They're Classes, Speeches, or Entertainment"](https://api.video/blog/video-trends/why-you-should-caption-your-videos-whether-they-re-classes-speeches-or-entertainm/) if you want all the details and statistics for why you should consider captions for your video content. Another great reason to add captions, is it's easy to do with api.video and Maestra! Let's get started. 

## Prerequisites

* [api.video account](https://dashboard.api.video/register)
* Maestra account (click the blue **Get Started Free** button)
* Sample video with spoken audio (we used one of Doug for this - https://www.youtube.com/watch?v=O3C7_kgwrPY, but any video is fine as long as it has clear audio) 

Maestra, auto captions, subtitles, caption a video, subtitle a video

maestra1.png

1. Click **New Subtitle** to bring up the upload panel.
2. On the upload panel under Upload your files, click **My Device**. 
3. For the Select audio language section, we choose **English** because the video is in English. The drop-down offers a 'Most Used Languages' section and an 'All Languages' section. 
4. You can choose different settings. For this walkthrough, we choose **Translate captions to another language** and then for the target language, choose **Spanish**. If you want different settings you can put those instead. 
5. Click **Submit**. 
6. Your video will start transcribing. Once it's complete, click on the title of your video. You can see how well your transcription came out. In this case, it came out pretty well.

maestra3.png

7. The next step is to export a copy of the file with the captions we want. Click the **Export** button in the upper right corner. You'll get a screen listing various choices, including downloading a video with all your captions included. We just want to get a WebVTT file for this walkthrough.
8. Make sure you are on the **Subtitle** tab. 
9. Under Languages, check the **English** and the **Spanish** box. 
10. Click **WebVTT** to download your caption file. The first time you click it, it will say **Ready**. The second time, it downloads a **.zip** file with your information in it. 
11. When you open the **.zip** file, you'll see a caption file in English and one in Spanish. Save these. 

## Add the Video to api.video
We need to add our video to api.video before we can caption it. You have a few choices available to you: 

* [Delegated Uploads for Videos Large and Small](https://api.video/blog/tutorials/delegated-uploads-for-videos-large-and-small-python/) - This tutorial shows you how to use a delegated token to upload a large or small file using Python.
* [Upload a Video From Your Computer](https://api.video/blog/tutorials/upload-a-video-from-your-computer-with-the-api-video-api-python/) - Upload a video under 128 MB from your computer using Python. 
* [Upload a Video with the api.video API Using a Public URL](https://api.video/blog/tutorials/upload-a-video-with-the-api-video-api-using-a-public-url-python/) - Transfer a video from a public URL to api.video

You can also use a no-code method:

1. Open the api.video dashboard.
2. Click **My videos**.
3. Click **Upload**. 
4. Add your video. 

## Use the Captions Endpoint to Add Captions to Your Video
We can now take the files Maestra generated for us and add them to our video. Here's the code sample we're going to use to do it: 

The code sample hard codes the videoId - but if you want you can retrieve it programmatically. A design where a VTT file's title somehow matches the video's title and then you grab the videoId might be a good way to go. 

In our demo, everything is set up to try to handle a situation where you have multiple caption files. We assume a naming convention like this: 
```title_language tag.vtt``` 

So samples of this would be: doug_en-GB for English from Great Britain and doug_es-ES for Spanish from Spain. 

The language tag in each case is a BCP 47 tag. The appropriate tag is at the end of each file so that it can be sliced from the file name and used in the caption upload. Using Python's regex and os modules we search for every file in the current directory that ends with '.vtt'. If it ends with this, we then retrieve the language tag from the end of the title, open the file in binary, then append the tag and file to a POST request to add a caption. We also modify the URL - it needs to include the videoId and the language tag for the language we want to add. You can see how that's built in the sample.

We have two caption files, so we loop through our .vtt files and send each one to be added. For each successful addition of a caption file, we get a response that looks similar to this: 

```
{
	'uri': '/videos/vi6FZib80ZrC8q73AekJqNDH/captions/es', 
	'src': 'https://cdn.api.video/vod/vi6FZib80ZrC8q73AekJqNDH/captions/es.vtt', 
	'srclang': 'es', 
	'default': False
}
```

* uri - the unique link that you add to ``` https://ws.api.video ``` to reach the video caption file (you must authenticate to view this, so you can't paste it into a browser to see it) 
* src - the location URL of the file
* srclang - what language you're using, written shorthand (instead of es-ES it would be es) 
* default - whether this is the default language for the video 

If you want to make a particular language the default caption, you can specify the language by updating a caption. 

## Check Your Work
You can retrieve details about your captions, but an easy way to check is to look in your dashboard: 

1. Go into your Videos section and click your video.


screen-shot-2021-03-22-at-11-42-19-pm.png

2. Click the **Captions** icon directly under the X. You'll see that you can add English or Spanish captions. Give it a try on your own video! 

screen-shot-2021-03-22-at-11-45-06-pm.png

Maestra does fairly well with captions, as long as the audio is clear. They offer a free trial for up to 30 minutes of video, so try them out yourself. Maestra lets you automatically create a variety of caption files, but api.video uses the WebVTT format, so you'll want that for any projects on our platform. 

If you want to create your own WebVTT file from scratch, Doug wrote a great post about how to do this here: [How to Add Captions to your Videos](https://api.video/blog/tutorials/how-to-add-captions-to-your-videos/)

## Show a Caption
You can see if a caption was already added with this code: 

## Show All Captions
If you want to see every caption for a video, you can do this: 

## Delete a Caption 
A caption can be removed with the following code: 

## Update a Video Caption
You can update a video caption to make it the default. The code for that would be: 

This is all the basics for using captions. Thanks for tuning in today! 
[Start builind now](https://dashboard.api.video/register)!

Add Captions to Your Video with Maestra and api.video

medium_screen-shot-2021-03-22-at-11-54-24-pm.png

small_screen-shot-2021-03-22-at-11-54-24-pm.png

thumbnail_screen-shot-2021-03-22-at-11-54-24-pm.png

screen-shot-2021-03-22-at-11-54-24-pm.png

thumbnail_JB-rond.png

JB.png

Jean-Baptiste

thumbnail_Arushi_.webp

Arushi_.webp

Arushi Gupta

api.video recently announced that it now offers [free encoding for all its users](https://api.video/blog/product-updates/video-encoding-pricing-update/)—a bold move perfectly aligned with our mission to democratize videos. 

&nbsp;

As a next step and to make things more transparent, we decided to take the help of some numbers and explain it to you.

&nbsp;

The natural thought behind video encoding is that it is expensive. That is mainly because encoding workloads demand substantial CPU resources, and CPUs can be quite costly. Consequently, encoding has traditionally incurred high costs and the higher the video resolution, the greater the CPU requirements, directly impacting encoding expenses. It seems logical that pricing should correlate with these factors, which is what experts typically anticipate.

&nbsp;

But that is not always the case. Read on to learn how we, at api.video, are making it possible to scrap video encoding costs for you all. 

## We build our own infrastructure
There are two common routes you can take for video encoding - Central Processing Units (CPUs) or Graphic Processing Units (GPUs). But let us accept that they are both not very affordable. Moreover, datacenter GPUs aren't primarily designed for video encoding but are rather now targeting AI tasks. And considering the popularity of AI, cloud providers are unlikely to reduce GPU prices because they can command higher rates from AI customers. That’s when a new alternative comes in: Application-Specific Integrated Circuits (ASICs). These are specialized chips (Video Processing Units) designed for specific workloads and have been recently in news due to Google developing its own VPU for YouTube called Argos.

&nbsp;

At api.video, we build our own infrastructure that has the most advanced VPUs. With these VPUs, we are able to save power consumption costs since the power consumption cost of VPUs is one order of magnitude lower than CPUs and GPUs. It is also easily possible to pack a lot of them in a single server. This increases their density and therefore, reduces the number of servers. 

&nbsp;

In a nutshell, VPUs help you to encode videos at scale without costing you too much, and that is exactly why we at api.video, made the move to use VPUs for video encoding.  

## Understanding encoding costs on VPUs

api.video uses VPUs built by [Netint Technologies](https://netint.com/). Let's understand the costs with a 1080p30 video. To simplify the case, I will assume the source video codec is h.264. The output videos after transcoding will be five h.264 renditions for ABR: 1080p30, 720p30, 480p30, 360p30, 240p30.

&nbsp;

For a real time transcoding, let's try to sum up the number of MP/s (Megapixel per second) it represents. For the above output, it represents 62 MP/s + 28 MP/s + 12MP/s + 7MP/s + 3MP/s respectively for 1080p30, 720p30, 480p30, 360p30, 240p30 renditions. We need an encoding capacity of 112 MP/s for real time transcoding. Let us assume that the transcoding cost on VPUs is proportional to the number of pixel per frame (whatever the frame resolution) for the sake of simplicity and one VPU of Netint is able to encode 2000 MP/s in h.264. In reality it is a bit more complex but let’s take these as the numbers for a rough idea. 

&nbsp;

Now, as per the above assumptions, we can encode 2000/112 = 17 minutes of videos (all rendition included) per minute. Below is a table summarizing the minute cost for a server with 4 VPUs. The cost of the server is $10k and the amortization for such a server is 3 years. The electricity cost will be approx. $1000 per year (420w at $0.30 / kWh) at full consumption. Let us see what is the cost of 1 minute of a 1080p30 video transcoded to 5 renditions.

&nbsp;

(The cost is split taking into consideration the average usage of the server per day)

&nbsp;

| Avg. usage of the server in percentage | Minutes encoded over the amortization period | Cost per minute transcoded (minutes / cost of server + electricity) in $
| ------------- | ------------- | ------------- |
| 0,50%       | 536112       | 0,020
| 5%   | 5361120        | 0,002
| 25%   | 26805600        | 0,0004
| 50%   | 53611200        | 0,0002
| 90%   | 96500160        | 0,0001

&nbsp;

If we use the server at only 0.5% per day (i.e ~7 min per day fully loaded) the cost per minute would be at $0,020.

&nbsp;

If on an average, this server is loaded at 25% (6 hours a day) the cost per minute would be 1/150 of our previous price.

### What about video quality?
Hardware encoded is always associated with quality losses in the head of many video engineers. But that was probably the case decades ago.

&nbsp;

Not anymore.

&nbsp;

Let’s see how VPUs compete with CPUs in terms of quality by taking a video under [Creative Commons license](https://en.wikipedia.org/wiki/Creative_Commons): Caminandes 2.

&nbsp;

We have uploaded its 1080p30 version via our API and will compare the quality output with a CPU encoded video with this option **-b:v 4400k -preset medium** These parameters generate a rather good quality.

&nbsp;

**ffmpeg -r 30 -y -i input.mp4 -c:v libx264 -force_key_frames 'expr:gte(t,n_forced*4)' -b:v 4400k -preset medium -c:a copy output.mp4**


&nbsp;

Here are the quality metrics (higher is better):

|                  | VMAF (avg) | PSNR (avg) | SSIM (avg) |
| ---------------- | ---------- | ---------- | ---------- |
| api.video (VPUs) | 95.92      | 48,07      | 0.9888     |
| ffmpeg (CPUs)    | 95.33    | 48.69      | 0.990     |


The quality metrics are very closed and report a high score. The VMAF is slightly better through VPU encoding.

&nbsp;

In conclusion, this pricing update reflects our commitment to enhance the video streaming experience for everyone - be it individuals or organizations looking to build their video solutions. We firmly believe that by making video streaming more accessible, we empower creators, businesses, and enthusiasts alike to embark on their video streaming journeys with ease. 

&nbsp;

_To know any other details, [talk to our team ](https://meetings.hubspot.com/apivideo/talk-to-us) and we are here to help you out._
 


Free video encoding: Let's talk numbers

large_Frame 427319242 (1).jpg

medium_Frame 427319242 (1).jpg

small_Frame 427319242 (1).jpg

thumbnail_Frame 427319242 (1).jpg

Frame 427319242 (1).jpg

emilien.jpeg

Emilien Gobillot

api-video-blog-company.png

Company News

In today's world, where environmental responsibility is important, businesses are re-evaluating their impact on the planet. Sustainable practices are not just a choice; they're a responsibility. When it comes to video encoding, a crucial aspect of content delivery in our digital age, there's a technology that aligns perfectly with this responsibility - ASICs. These Application-Specific Integrated Circuits (ASICs) not only promise more efficient video encoding but also contribute majorly to a lower carbon footprint.

&nbsp;

That’s why, api.video has gone forward and switched from CPU based encoding to ASICs based encoding.

&nbsp;

This blog is intended to tell you more about this switch. 

## The rise of ASICs in the video industry

In the past few years, the internet's growth sparked a rise in digital video demand. As platforms like YouTube and Netflix rose, companies leaned more toward CPU-based encoding due to its versatility. However, as streaming services gained popularity, CPU encoding's limitations started getting noticed. 

&nbsp;

Video encoding relying on CPU power is no longer a sustainable approach, as superior alternatives are now available that come without any compromises. A great example of this is Google. Google has developed its own Video Processing Unit (VPU) known as [Argos](https://9to5google.com/2021/04/22/youtube-google-custom-chip/) – a groundbreaking innovation. Through the integration of these VPUs, Google has significantly amplified transcoding capabilities per server, cut down operational expenses, reduced electricity consumption, and ultimately improved the Total Cost of Ownership (TCO). Following in Google's footsteps, Meta has also embraced this transformation. 

&nbsp;

What does this mean? It simply means that ASICs reduces the resource consumption of video encoding (see graph below) and that’s why companies are adopting it. 



MPixel_s per Watt encoded to H.264 (Higher is better)(1).png

Now what is the secret behind these VPUs that are replacing CPUs? VPUs are, in fact, ASICs-based chips specifically engineered for a singular purpose: decoding and encoding video frames. They support various codecs such as h.264, vp9, and AV1, among others. 

&nbsp;

Their power consumption is lower than that of CPUs, and their capacity is substantially greater. Consequently, you can expect VPUs to reduce electricity consumption by 10x to 100x, depending on the codec and the specific VPU in use.

&nbsp;

The best part is that the quality of the video output in VPUs matches that of CPU encoding. (We will delve into the technical details in an upcoming blog post.)

## What made us start ASIC based encoding at api.video

- ASICs also known as VPU (Video Processing Unit) are one order of magnitude more power efficient than CPU based transcoding. 

&nbsp;

- Using dedicated hardware allows us to increase the density which in turn reduces our environmental footprint. As a corollary, it increases our transcoding capacity.

&nbsp;

- Specialised hardware helps improve the TCO (Total Cost of Ownership). When we increase the capacity and density of a server, there is a fewer requirement of servers and less rack space. So it reduces capital expenditure and operational expenditure. 

## What does this mean for you as a customer

In today's environmentally conscious world, the impact of technology on our carbon footprint is a growing concern. This is where ASIC becomes a game-changer. 

&nbsp;

But, you might wonder, what can you, as a customer, gain from embracing ASICs technology?

&nbsp;

- **First and foremost, ASIC brings sustainability to the forefront.** By significantly reducing energy consumption compared to generic hardware, ASIC chips align perfectly with your green initiatives. Your carbon footprint shrinks, making a substantial contribution to a better environment.

&nbsp;

- **Secondly, [you get encoding at ZERO cost ](https://api.video/blog/product-updates/video-encoding-pricing-update/) with api.video.** Yes, it is because of ASICs that we are able to reduce our TCO and offer you video encoding at no cost. This means that if you choose api.video for video streaming, you save on the cost of encoding completely. 

&nbsp;

- **Thirdly, ASIC's efficiency translates to faster video processing.** This means that with ASIC’s optimized infrastructure, your complex videos are encoded faster. 

## Stepping into a greener future with ASICs

To create the environmentally responsible future we desire, changes in video encoding and distribution are imperative. ASICs-powered encoders represent a breakthrough, offering enhanced density, performance, and cost-efficiency. These advancements will ensure video applications to scale economically while significantly reducing their environmental footprint.

&nbsp;

With this initiative, let us pledge to make a greener and a better environment around us!

&nbsp;

_[Sign-up](https://api.video/) with api.video today or [talk to our team](https://meetings.hubspot.com/apivideo/talk-to-us) for more information._


Introducing ASICs-based encoding at api.video

small_ASIC_eco.jpg

thumbnail_ASIC_eco.jpg

ASIC_eco.jpg

video industry

Video trends

**The comeback of specialized hardware and its impact on the video industry**

Over the past few decades, the trend in computing has been toward general-purpose computing systems that can run a wide variety of applications. This has led to the widespread use of [CPUs and GPUs](https://www.intel.com/content/www/us/en/products/docs/processors/cpu-vs-gpu.html). However, there has been a recent resurgence of interest in specialized hardware, which is designed specifically to perform one or a few tasks extremely efficiently. In this blog post, we will explore the reasons behind this trend and some of the critical examples of specialized hardware being used in the video industry today.

**Why is specialized hardware making a comeback in computing?**

Specialized hardware in the computing industry refers to computer components or devices designed for a specific purpose, such as application-specific integrated circuits (ASICs)  or systems-on-a-chip (SoCs) . These hardware components are optimized for their specific task, resulting in faster and more efficient performance than general-purpose hardware.

Several factors have contributed to the recent resurgence of specialized hardware in computer science:

* **High efficiency : Why we want it quick and ressource-efficient**

One key driver is the increasing demand for high-performance solutions. Artificial intelligence, machine learning and video processing are domains where CPUs are far from being the right solution. Regarding AI workloads, training, and running models are more efficient on GPU and even better on specialized hardware like Tensor processing units (TPUs). Google has been the first to design TPUs. These ASICs (Application Specific Integrated Circuits) outperform the CPUs.

Why are CPUs outperformed ? In early 2023 commodity servers come with 1 or 2 sockets and maximum 96 cores per socket for the x86 microarchitecture (128 for ARM). On the other hand, a server with a mid range CPUs can receive several ASICs/TPUs on the PCIe ports. Those boosted systems outperforms by a lot the CPUs based system. The TPUv4, in terms of Tflops is 2000x faster than a laptop according to Google.

The benefits of a specialized hardware is that it provides better performance, higher density and a lower energy consumption than the classic CPUs.

In most cases, TPU/ASIC > GPU > CPU on the 3 criteria : performance, density, and energy savings.

* **Total Cost of Ownership (TCO): Why It's Worth the cost**

Specialized hardware exhibits smaller size, higer speed, and greater electrical efficiency. As a result the density increases and the number of computing units decreases. At the end, the TCO is improved. After the switch to ASICs based VCUs (Video coding unit), Youtube is [reported](https://www.semianalysis.com/p/google-new-custom-silicon-replaces) to have saved millions of CPUs ! At this scale you also save data centers 💰

**How specialized hardware is changing the game in the video industry**

In the video industry, one of the most computationally intensive processes is video transcoding, especially for high-quality videos. Transcoding decodes a video from one codec and encodes it to another, such as from H.264 to H.265. This process can also involve changing other video parameters like resolution, bit rate, frame rate, etc. This has led to a need for fast and efficient video transcoding solutions without sacrificing the video quality output.

Transcoding is a service api.video provides in addition to hosting and delivery. Via an API call, a video is uploaded, and then the URL of the video is returned immediately. Note that high resolution and new codecs increase the computational cost.

Similarly to Artificial Intelligence (AI), several types of hardware are commonly used in video transcoding applications:

1. ASICs (Application Specific Integrated Circuits): Video ASICs are specialized hardware accelerators designed specifically for video processing tasks, such as video encoding/ decoding / transcoding. They are sometimes called VPU (Video Processing Unit) or VCU (Video coding Unit). They significantly improve performance over traditional CPUs, particularly for high-resolution or high-frame-rate video. Alphabet, the mother company of Google and YouTube has designed its own ASICs : codename Argos. For a system with 20 VCUs, the TCO has decreased by a 33x factor for VP9 encoding, and throughput increased by a 100x factor!

Facebook/ Meta made the same move to specific hardware. They partnered with silicon vendors to [design custom ASICs](https://engineering.fb.com/2019/03/14/data-center-engineering/accelerating-infrastructure/).

The electric consumption of an ASIC is around a few watts.

2. FPGAs (Field-programmable gate arrays): FPGAs are programmable hardware devices that can be customized for specific applications, including video transcoding. They can provide significant performance improvements over traditional CPUs for certain types of video transcoding tasks, such as simultaneously encoding or decoding multiple video streams. Twitch is using an [FPGA from Xilinx](https://blog.twitch.tv/en/2018/12/19/how-v-p9-delivers-value-for-twitch-s-esports-live-streaming-35db26f6322f/).

The electric consumption is around 25 W for a PCIe card

3. Graphics processing units (GPUs): GPUs are another type of hardware. This hardware is more generic than FPGA and ASIC, but specialized video encoders/decoders are added to these cards. Nvidia was the first company to build a datacenter GPU for transcoding. Intel enters the market in late 2022.

The electric consumption is generally around 70W.

Regarding energy consumption ASICs > (are better than) FPGAs > GPU > CPU. This order is the same for the transcoding speed.

**Reducing the carbon footprint of video transcoding : api.video’s approach**

At api.video we are really focused on the energy consumption of our transcoding pipeline. We want to minimize the ecological impact of video transcoding while keeping the transcoding speed high. The infrastructure team has performed multiple benchmarks, and here are the results.

Those numbers are based on public information (marketing sheet) for the GPUs and FPGAs and real benchmarks for the CPU and ASICs. The quality of the video's output could change the results slightly, but we clearly see a winner regarding power efficiency. In a future blog post, we will share precise benchmarks about the ASICs vs. CPU battle with you. Stay tuned.

Along this article, we have seen the resurgence of dedicated hardware in computer science is driven by a growing need for high-performance computing, particularly in fields like artificial intelligence, machine learning, and video transcoding. Dedicated hardware can provide better performance and energy efficiency than traditional general-purpose computing units, making it an attractive option for many applications. As computing continues to evolve, we will likely see more specialized hardware being developed for specific tasks, driving innovation and progress in the field. 

Our video API allows you to add videos to your products while prioritizing the reduction of your carbon footprint. [Join us](https://api.video/) and take part of the transition to an environmentally responsible video infrastructure.

The comeback of specialized hardware

Frame 427319155.jpg

api.video

Modern technology has been helpful for an increasingly fast and simple method of consuming various types of video media, whether it’s a YouTube video, our favorite shows on Netflix, or even catching up with friends across the globe on Zoom. Despite the relative ease of doing anything related to video, a few complex processes take place behind the scenes, away from public view. One such process is video encoding.

Video encoding basically makes the world go around in regards to anything related to video and video content. Thanks to the technologies behind the video encoding process, it has become much easier for people and companies to share video content on the internet. But what exactly is video encoding, and what happens during the process? We’ll take a closer look at this and much more in this handy guide to video encoding.

## What is video encoding?

In a nutshell, video encoding occurs when you take raw video footage, either from a digital camera or an analog film camera, and digitally compress it to make it a more manageable file size. Video encoding happens daily in both professional and personal capacities, and many people don’t realize it.

But, without encoding, services like Netflix and YouTube would not exist – or, at least, not in the same way that it does today. Without it, we couldn’t send videos of our beloved pets to our friends and family as easily as we can today.

## Why is video encoding used?

There are a variety of reasons why video encoding is used, but all factors point to the single function of video encoding – **compression**.

This is done to ensure optimal performance and compatibility with a selected suite of software and hardware, be it for DVD/Blu-ray playback, mobile viewing, online video streaming, or general video editing. A file's video and audio information undergo transformation and compression during the encoding process, all in accordance with the requirements of the selected encoding standard.

On a professional level, the ability to compress raw video into more manageable sizes makes it easier to transmit video content such as training, promotion, presentation, and so on over the internet. 

On a personal level, video encoding makes it much easier to send videos taken from your phone directly to friends and family. Most modern-day personal devices have built-in video encoding capabilities to allow for this to happen without a second thought.

To put things in perspective, uncompressed or unencoded video can have a data rate that’s as low as 3,000 Mbps and as high as 12,000 Mbps, depending on the length and quality of the video recorded. 

**Without encoding, it would take up to days for anyone to not just transmit video, but to be able to consume it, too.**

## Differences between video encoding and video transcoding

You need to be familiar with two more [essential terms related to video encoding](https://api.video/what-is/) – transcoding and codecs.

Transcoding relates to the conversion from one digital encoding format to another. It takes the already encoded video file, decompresses it, and then alters it before re-encoding or compressing it into a different codec. Codecs are what allow encoding to occur in the first place. They are software or hardware that gives us the ability to compress video to make them more easily stored and delivered tightly.

While you may hear “encoding” and “transcoding” used interchangeably, the two terms actually mean different things. Putting it succinctly, encoding is the initial process of compressing a video from a source – such as a camera – into a codec, while transcoding takes an already encoded video file to convert it into a different codec.

## Examples of video codecs

In order to understand video encoding, you must first be familiar with two interrelated terms: [video codecs and video formats](https://api.video/blog/product-updates/every-video-format-codec-and-container-explained/). These also tend to be used interchangeably, but much like the terms encoding and transcoding, they refer to two different things.

Video formats are the type of files in which the compressed video/audio is stored. Also known as a “container”, you can tell what a video format is by looking at the file’s extension — the three to four characters that sit after a period in a file name. Here are some of the most common video formats used today:

* MP4
* FLV
* MOV
* MKV
* LXF
* MXF
* AVI
* WebM
* QT

On the other hand, **the codec is short for “Coder / Decoder” (compression / decompression)** and relates to the video compression algorithms that allow encoding to happen. Over the years, codecs have gone through multiple iterations as it coincides with the increasing sophistication and rise in the quality of filmmaking. 

If you’re a content creator, you might be aware of some of the video codecs that exist today:

- **H.264 – also known as AVC, this is the most widely-used video codec available on every platform and mobile device.**
- H.265 – also known as HEVC, stands for High-Efficiency Video Coding, and it’s slowly overtaking H.264 as the standard. This codec can compress video much more efficiently than its predecessor.
- **VP9 – is an open-source, royalty-free codec developed by Google and is considered the direct competitor of H.265. The video compression codec VP9 was created to reduce file sizes, making streaming videos simpler.**
- **AV1 – is another royalty-free, open-source codec released in 2019 by the non-profit Alliance for Open Media. It was developed to become the successor to Google’s VP9 and contend with HEVC more directly.**

## How do different technologies handle video encoding

As you may have suspected, there are a majority of ways that different technologies handle the video encoding process. Let’s take a look at the most common technologies that use video and how video encoding works on each of them:

### Video editing software

When it comes to video content creation, a majority of people will use one of two video editing software — Adobe Premiere Pro or Apple’s Final Cut Pro. Both of these video editing software handle video encoding in very similar ways: when exporting the finished video.

Depending on which device the video content is recorded on, it will already be encoded and formatted according to the settings of the device. For those using iPhones recording 1080p video at 25 frames per second (FPS), for example, the iPhone will automatically encode the video using H.264 and contain it in a .mov file format. The video editing software will “open up” the container to get to the encoded, compressed video file within so the editing process can begin.

After editing the footage is complete, it will need to be exported, which typically concerns video encoding. The edited raw media taken from a recording device such as a camera will be encoded via the codec of the person’s choosing before being put into a .mp4 container once they’ve hit “export”. As we’ve mentioned before, the most common codec used in video content creation is H.264 for HD videos, with 4K videos using H.265. 

### Websites

Different websites utilize different techniques to handle video encoding – with a majority of the major sites like YouTube, Netflix, and so on using their own technologies to handle the process. A majority of social media websites allow you to upload video files directly onto the site to share, although most of them require the files to be saved in specific containers. 

These websites will take your video file and transcode it before using their own systems and serves to re-encode it to match multiple display resolutions. This process will happen regardless of your video file's original codec and settings. Different websites have different processes, but companies that don’t have the capacity to build their own video encoding systems can use a third-party application programming interface (or API) to handle this process. These APIs act as [dedicated video encoder](https://api.video/what-is/video-encoding/) that allows companies to add on-demand videos to their websites more efficiently.

Using [api.video](https://api.video) as an example, all of the videos submitted to the platform will be transformed into H.264 codec in an MP4 container. This may be done using transmuxing and/or transcoding.

We expect the video bitrate to be lower than 16 Mbps for up to 1080p resolution and 50 Mbps for up to 4K resolution. We accept any bitrates, however, we will scale them down to the limits mentioned because anything above is usually challenging for most viewers’ connection to watch.

### API

The ability to generate, store, and distribute video is made possible via a video API. [api.video](https://api.video)’s solution can be tailored to suit any specific need. 

The backend process of video on demand (VOD) is exceptionally complex, even if you’re a software programmer specializing in video. It is necessary to encode, package, and typically transcode the data before sending it to any of several possible destinations. All of these things, and more, may be done with minimal fuss using api.video.

Our API basically keeps the complexities of streaming media hidden from view, so you can rapidly develop apps with as much control as you need. This saves time and effort so developers can concentrate on making the product.

## Conclusion

As you can see through this video encoding guide, a lot of work goes into making the video you watch and the video you share possible. Without video encoding compressing raw video footage, it could take days to upload and transmit video content over the internet and perhaps even longer to be able to download and enjoy them. 

The best part about encoding at api.video is that is offered at ZERO cost. You will only be charged for delivery and hosting of your videos, and the encoding will be free. Now integrate your videos in minutes with api.video or [contact us](https://api.video/contact/) for more information.

A Guide to Video Encoding & Video Codecs

poster-3.png

Doug Sillars

Once I upload my video, how quickly will it be ready to be viewed?

Our reply to this question has always been “it's really fast.”  And it is really fast. But, the dev team gave me access to the backend database, and pointed me to a few tables that might be helpful (thanks to Thomas Persohn for your patient help!)

Thus armed, I waded into a sea of data to better understand how fast our videos are encoded at api.video

## Encoding

When a video is uploaded to api.video, it is re-encoded to a HLS stream, with several different video dimensions and bitrates.  This allows api.video to deliver properly sized video to all users - no matter the device or network connection. (Read our post on [Responsive video delivery](https://api.video/blog/video-trends/responsive-video-delivery/) to learn more.)

> Summary:  All videos are encoded at 240p, 360p, 480p, 720p, 1080p and 2160p. However, the videos are only encoded up to the initial size of the video (so if the original video is 720p, there will not be 1080p or 2160p versions available). 

**FYI:** For our customers, encoding is absolutely free – we offer adaptive bitrate encoding at zero cost. 

How long does this step take? If a customer uploads a video to our service - they want to know how efficient api.video creates the content for viewing.

### Data in the study

We are constantly making adjustments to our infrastructure to speed the encoding step of our video (and that is one reason this post is dated 2H 2020 - we expect to be faster in early 2021). The last major adjustment was made in mid October, so the data presented in this study from every video uploaded to the api.video service between 15 October and 2 December 2020.

### Parameters that affect encoding

There are 2 major parameters that affect the speed of encoding a new video stream: the output dimensions and the length (duration) of the video.  

#### Dimensions

The output video dimensions have a huge impact on video creation - a 3840 × 2160 (or 4K or 2160p) video has millions more pixels than a 320x240 (240p) video, so it takes a lot longer to create.  In general, the videos exit the encoding process from smallest to largest.

#### Duration

If a video is 30 frames per second, and is 60 seconds long, there are 1800 frames to be created.  If a 30 frame per second video is an hour long 3600s), there are 108,000 frames to be created, so the longer the video - the more time for creation.

## Analysis

To better understand the encoding time, I divided the data by the size of the output video size, and looked at 2 lengths of video  - those under 5 minutes, and videos that are 45-75 minutes long (we are often asked how long a 1 hour video takes to encode).

I calculated encoding time for each bucket of video using percentiles.  

> Quick review - percentiles break the data into 100 evenly sized segments, so the 25th percentile is when 25% of the videos have been encoded. The median is the 50th percentile, and is when 50% of videos have been encoded.  We report here to the 95th percentile for video encoding.

### Short videos - under 5 minutes long

Many of the videos uploaded to api.video are short - under 5 minutes long.  These videos are generally ready to play in a few seconds:



The above chart has a lot of data, the 25, 50, 75, 90 and 95th percentile encoding times for all 6 variants of the video that api.video creates.

The median video is ready to play (at 240p) in 5.6 seconds, but a 720p version will be ready in 15s after encoding begins, and the 4K version will be ready in 37 seconds.

95% of all videos (under 5 minutes) will be playable in 32.6s, and will have 1080p versions ready in just over 2 minutes (140s).

### Long videos - 45 - 75 minutes long

Our most frequently asked question on encoding is "how long for a 1 hour video to be encoded and ready?"  Here are the numbers:


Observant viewers will see there are no 4K videos in this report. At this time, there are very few 4K streams that reach the 1 hour timeframe, and the data was quite noisy.  Hopefully, more of our 'long uploads' will add 4K support, so we can add this metric in our next update.

The median hour long video (red line) will be ready to play (at 240p) in just over 9 minutes (555s), and a 720p version will be ready about 18 minutes after encoding begins (1099s).

95% of hour long videos will have a 240p version ready in 33 minutes, and 720p in 54 (3230s).  the 1080p version will be available for 95% of videos in 108 minutes,

## Conclusion

Short videos will be ready to play - even at high resolution - in under a minute: the median 4K encoding for a short video is 37s. 

Hour long videos take longer to encode, and the median 720p video will be ready in 18 minutes.  95% of 720p videos will be ready to play in 54 minutes.

This is really fast! You can have responsive streaming video ready for your customers in just a few minutes with a simple upload!

That said, our team is working hard in the background to improve our infrastructure to make our encoding speeds even faster! 

We're really excited to have hard numbers to share with you on our encoding speeds, and we cannot wait to re-benchmark this data in 2021 to see how much faster your videos will be encoded as we improve our service.

Do you have questions about api.video or video encoding? Reach out on our [community page](https://community.api.video).


How fast does api.video encode video? 2H 2020 data

gif.jpg

ASICs-based encoding: Building a greener tomorrow through reduced carbon footprint

codec

video create

At api.video, our goal is for video to be easy and affordable for anyone to build, be it individuals or organizations. We understand that achieving this goal means reducing costs at some stage of the video streaming process. That’s why, we now offer adaptive bitrate encoding for your videos at zero cost. 

&nbsp;

Yes, you heard me right. 

&nbsp;

**Encoding videos will be absolutely free for all video qualities (1080p or 4K) at [api.video](https://api.video/) - no hidden calculations, footer notes or tricks.**

(Check out this [video](https://www.youtube.com/watch?v=ouosgLbW7Ts) for more details) 


## A step towards making video streaming affordable

Video encoding is crucial as it makes it possible for videos to be shared and played smoothly on the internet. It is why we are easily able to consume various types of video media, whether it’s a YouTube video, our favorite shows on Netflix, or even catching up with friends across the globe on Zoom. Video encoding basically makes the world go around in regards to anything related to video and video content.

&nbsp;

We at api.video recognize that. From [increasing the transcoding and playback speed ](https://api.video/blog/product-updates/2021-in-review/)to building [specialized hardware like ASICs](https://api.video/blog/video-trends/the-comeback-of-specialized-hardware/) cards to increase our transcoding capacities, we've been working to make video streaming easier for you every day. And after dedicating ample time to engaging with our customers and learning about their concerns, free encoding seemed to be the next step in this direction. 

&nbsp;

So, we worked tirelessly behind the scenes to give you what no one else will - free encoding for all video qualities, be it 360p or 4K. 

## How does free video encoding benefit you as a customer

The benefit is straightforward: you save a LOT of money!

&nbsp;

- With free video encoding, you will have one less thing to worry about. As you know, you pay for three things for streaming videos — encoding, hosting, and delivery – out of which encoding is the most expensive, especially if you have a lot of videos. Free video encoding will allow you to focus your attention and resources to what is most important.

&nbsp;

- As the video needs of your app users grow, you might need to scale up your encoding capacity. Free video encoding services will give you the power to scale without any additional costs, meaning your users can handle more videos without increasing your expenses.

&nbsp;

- You can [migrate from your previous provider to api.video](https://api.video/compare/azure-media-services/) without paying an ‘entry tax’ to us. With free video encoding, you no longer need to spend money on encoding videos with a new provider when you have already paid for encoding with an older one.

&nbsp;

Now with all the saved cost, you can allocate your resources and money to a place where it is actually important – building your product and delighting your users. 

## How to get started

To use the free video encoding benefit, getting started is easy. 

&nbsp;

- If you’re a new user, [sign-up](https://dashboard.api.video/register) for a free sandbox account and start uploading your videos
- If you are looking to migrate from another vendor, [import](https://import.api.video/) your videos from your current vendor
- If you have any questions, [talk to us](https://meetings.hubspot.com/apivideo/talk-to-us) by booking a slot in our calendar

&nbsp;

To know more about our[ features](https://api.video/features/), [pricing](https://api.video/pricing/) or ask any other questions, [talk to our team ](https://meetings.hubspot.com/apivideo/talk-to-us)and we will help you out. 

&nbsp;

Or, you can straightaway [sign-up](https://dashboard.api.video/register) for a free sandbox account and check our product out for yourself. 


Huge pricing update: Introducing video encoding at no cost

small_Blog_Zero Cost.webp

thumbnail_Blog_Zero Cost.webp

Blog_Zero Cost.webp

Encoding and transcoding are often used interchangeably but they have slightly different definitions. **Encoding is the initial process of converting raw video files into a specific digital format or codec.** It involves compressing and packaging the video data, often to reduce file size while maintaining acceptable quality. Encoding prepares the video for storage, transmission, or playback.

&nbsp;

**Transcoding, on the other hand, involves converting a video from one digital format or codec to another.** This is typically done to optimize the video for different devices or platforms, adapt to varying network conditions, or ensure compatibility with specific playback requirements. Transcoding occurs after encoding and often involves changing resolution, bitrates, or formats without altering the content itself.

## What goes on behind encoding a video?

It's easy to say that encoding is when you go from an _uncompressed source_ to a _compressed source_, but you may ask, what exactly do compressed and uncompressed sources mean?

&nbsp;

Uncompressed sources are video files that contain data that comes directly from a camera sensor vs. encoded video. In the digital space, it's SDI (Serial Digital Interface) or HDMI (High Definition Multimedia Interface). Both of them are popular standards. You'll find HDMI in places like your GoPro camera, or a mini camcorder. These days, you might also find HDMI in professional settings, but SDI is more common due to its reliability. Another example of an uncompressed source would be something analog, for instance, VHS tapes.

&nbsp;

A compressed sources, on the other hand, are video files that have undergone compression during the encoding process. Compression involves reducing the file size by removing unnecessary information or encoding the data in a more efficient format. This process results in a smaller file size, making it more manageable for storage, transmission, and playback.


## What are the types of transcoding methods?

There are three types of transcoding, depending on what you are trying to do to get a video to suit a particular browser, player, or platform:

* **Lossless-to-lossless** - This type of transcoding maintains the quality of your video across formats but allows you to take advantage of better hardware or compression algorithms. 
* **Lossless-to-lossy** - This type of transcoding will decrease your video in quality, but it will benefit you in ways such as – you will get a smaller and/or faster playing file, or a file that is compatible with the requirements of a particular platform, player, or browser.
* **Lossy-to-lossless** - Sometimes people think this means they are regaining quality. This isn't the case in this type of transcoding. If you transcode from a lossy format to a lossless format, all that it means is that you will not lose additional quality in the conversion process. You will not regain data you already lost through compression.

## Codecs for encoding and transcoding

For both encoding and transcoding, you will need to make use of codecs. A codec's job is to compress and decompress video files. It's right there in the name -  **co**mpress **dec**ompress or encode decode. So basically, codec is an algorithm that takes the video and shrinks it or changes it into a format that makes it compatible with the requirements of wherever you want the video to play. There are many codecs because there are many ways to compress a video or livestream for playback.



## What is transmuxing?

Now that you know the difference between encoding and transcoding, let's throw one more term in there - transmuxing. Transmuxing is when you change the container for a video instead of the format. It's a way of repackaging a video to make it compatible somewhere without changing what's in the file. 

&nbsp;

This process is faster than encoding or transcoding and takes less computing power because you only change the container, not the file. It's great when you need to quickly make something available, but the downside is that it doesn't handle things like making multiple video resolutions available. If you choose a container type that's incompatible with your video file, you may also cause compatibility issues, resulting in not being able to play the video.

## In closing

* **Encoding** - Encoding happens when you compress a raw data file from a video camera sensor or an analog source like a VHS tape. 
* **Transcoding** - Transcoding happens when you take an already compressed video file and change it to another format.
* **Transmuxing** - Transmuxing happens when you change the container of a video file but leave the video file untouched. 

We hope that explains the difference between encoding and transcoding clearly. 

_If you are looking for an affordable video API solution that does not burn a hole in your pocket for transcoding and encoding videos, check out our offerings on our [homepage](https://api.video/) or [sign-up for a free account here](https://dashboard.api.video/register)!_

Encoding and transcoding: what's the difference? 

EncodingTranscoding.png

Huge pricing update! Introducing video encoding at zero cost

api-video-blog-video-trends.png

giphy (4).gif

shrink video.gif

large_EncodingTranscoding.png

medium_EncodingTranscoding.png

small_EncodingTranscoding.png

thumbnail_EncodingTranscoding.png

logo_avatar.webp

poster-1_2.png

large_poster-3.png

medium_poster-3.png

small_poster-3.png

thumbnail_poster-3.png

doug.jpg

Doug Twitter

Videos are generally ready to play in a few seconds

screenshot-2020-12-04-at-09-41-12.jpg

how long for a 1 hour video to be encoded and ready?

screenshot-2020-12-04-at-09-42-18.jpg

medium_gif.jpg

small_gif.jpg

thumbnail_gif.jpg

small_anthony.png

thumbnail_anthony.png

anthony.png

Anthony Dantard

As brands aim to establish their identity, setting themselves apart from the competition is important. With the widespread sharing and duplication of content, safeguarding your videos and promoting your brand has become crucial. This is where white labeling comes in. By personalizing and branding your videos, you can create a distinctive presence in the market, captivating your viewers and making a lasting impact.

&nbsp;

To make sure you retain your brand’s identity, we have built our white-labeling feature. A feature that ensures that you have complete control over the aesthetics and functionality of your video player while offering superior streaming quality. 
In this article, we will discuss how white-labeling with api.video can enhance your video streaming experience. 

&nbsp;

Let’s get started.

## Tailor your video player look to your brand

Your video player must be as unique as your brand is. With the api.video white-labeling feature, you get customization options that ensure your video player matches your brand aesthetics so that your audience gets a consistent experience.

&nbsp;

Alter the color scheme, adjust the player's behavior, or revamp the controls. With our versatile customization tools, you're always in the driver's seat!


large_player_theme_custom.jpg

medium_player_theme_custom.jpg

small_player_theme_custom.jpg

thumbnail_player_theme_custom.jpg

player_theme_custom.jpg

## Integrate the company logo into your video player

Your logo is the centerpiece of your brand and it must be present in all your marketing collaterals. With our white-labeling feature, you can display your company logo prominently on the video player, thereby ensuring that your brand is recognizable instantly.


large_Capture d’écran du 2023-05-26 10-56-24.png

medium_Capture d’écran du 2023-05-26 10-56-24.png

small_Capture d’écran du 2023-05-26 10-56-24.png

thumbnail_Capture d’écran du 2023-05-26 10-56-24.png

Capture d’écran du 2023-05-26 10-56-24.png

## Get personalized thumbnails for your videos

With our personalized thumbnails, capture your audience with a preview that aligns with your brand. When you use our 'pick or upload thumbnail' feature, you can choose a perfect snapshot to represent each video before it starts playing. Use captivating images that carry your brand identity and capture your audience's attention.


Video on demand

Live streaming

Analytics

Video infrastructure

Video player

See all features

Online learning

Short-form videos

Marketplace & E-commerce

Video messaging and recording

Quickstart guides

Documentation

Ecosystem catalog

Clients & SDKs

Community

Blog

Demos

Help center

Product updates

Latest product updates from api.video