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

As the year comes to an end, we wanted to take a moment to look back at everything the team released to help you build your video products (and to share a surprise)!

Let's start with our core principle: *make videos available worldwide in seconds*.
For years, it has been highly complicated to add video features to apps and platforms because of the various services you had to aggregate (ingest, transcode, host, deliver, analyze). 
Our goal is to bring you a dead-simple API to implement the entire video workflow in minutes and provide an exceptional experience to your end-users, whether they are creators or your audience. 
In 2021 we've welcomed users from **122 countries** (astonishing!) and have ingested **110%** more video minutes than in the previous year. 

## Providing the greatest video performances for your app

* All videos you send to us have never been transcoded faster. Our recent [benchmark](https://api.video/platforms-benchmark/) reveals that a 5-minute video is available for playback in 6 seconds with api.video. In contrast, other services take up to 60 seconds.

large_benchmark.png

medium_benchmark.png

small_benchmark.png

thumbnail_benchmark.png

benchmark.png

* Once the video is uploaded, your audiences expect an exceptional playback with no buffer or latency. We have been delighted to discover the [PlayerX benchmark](https://dev.playerx.io/compare/). Considering all B2B and B2C video platforms, api.video provides the greatest viewer experience on the Market!

**The best part of that? This is nothing compared what we'll bring you in 2022!**

## New features 

We've introduced a lot of new features, most of them inspired by your feedback 🙏
* After releasing live streaming in 2020, we added [private live streaming](https://api.video/blog/product-updates/new-beta-feature-private-livestreams/) to help your users broadcast their video feed securely into your app.
* [Progressive upload](https://api.video/blog/tutorials/progressive-uploads-with-the-api-video-python-client/) was released earlier this month to let you build recording features that your users can launch right from their browser or record a video directly from a video stream.
* Thanks to the [webhooks](https://api.video/blog/endpoints/webhooks/), you are now notified when on-demand and live videos are ready to be played.
* Clipping became available a few days ago. This new feature allows you to edit your videos right from the service without downloading them first.

## Reduce your workload and make api.video available in your CMS
To help you launch your product fast, we've added many new ways to implement [api.video](https://api.video) in your stack:

* 8 (yes...8!) [new clients](https://docs.api.video/) were published on our GitHub account: PHP, Python, Go, Java, NodeJs, C#, Android, and iOS
* If you are using a CMS to build your portal, you can now install our official [plugins for WordPress](https://github.com/apivideo/api.video-wordpress-plugin), [Contentful](https://docs.api.video/sdks/nocode/contentful), [Bubble.io](https://docs.api.video/sdks/nocode/bubbleio-plugin), and Moodle to allow your users to upload and share videos right from their backend.
* To enable customization of the video experience, we've also released standalone plugins for [analytics](https://docs.api.video/sdks/player/apivideo-videojs-analytics), the video uploader modules for [Flutter](https://docs.api.video/sdks/vod/apivideo-flutter-uploader), [Android](https://docs.api.video/sdks/vod/apivideo-android-uploader) & [iOS](https://docs.api.video/sdks/vod/apivideo-swift-uploader), and the live streaming modules for [ReactNative](https://docs.api.video/sdks/livestream/react-native-livestream-component), [Android](https://docs.api.video/sdks/livestream/apivideo-android-livestream-module), Flutter, and [iOS](https://docs.api.video/sdks/livestream/swift-livestream-library).

## New branding
You may have noticed our [new logo](https://api.video/blog/product-updates/new-logo-same-mission-connecting-people-through-unique-video-experences/) last summer, but there is more. 
Check out our [fully redesigned dashboard](https://dashboard.api.video/overview) that lets you easily switch between your environments, create, view, and edit videos. Plus, you can share the on-demand and live stream videos you're managing and access your KPIs and metrics! The new dashboard also lets you switch from one plan to another at any time as your needs evolve.

We hope you enjoyed reading through some of the major releases we've had in 2021 and that you've discovered some new features that you'll start using today. We are building [api.video](https://api.video) for you and with you: your ideas and feedback are essential to us. Let us know which new features you'd love to see us add in 2022 either in chat or by posting in our [community forum](https://community.api.video). 

On behalf of the whole api.video team we would like to thank our amazing community for all the feedback and support over this past year. We wish you all a wonderful festive period and a very happy New Year! ✨

large_apivideoteam.png

medium_apivideoteam.png

small_apivideoteam.png

thumbnail_apivideoteam.png

apivideoteam.png

## One more thing!

We couldn't end this review without a gift 🙂

You might have videos on your computer that you want to upload during your implementation, or you might need to iterate and quickly share different versions of your content without having to open & close WeTransfer again and again.

Do you remember the first time you used Dropbox and how magical it was to sync a local folder with them?

We're thrilled to announce the Windows and macOS clients!

- [Download the app](https://github.com/apivideo/api.video-desktop-synchronizer/releases/tag/v0.1.2), pick a local folder to sync, and add your API Key.
- Drag and drop videos to the folder.
- Voilà! The sharing links to your transcoded videos are ready to be use

2021 in review: video transcoding, playback and new features

2021-in-review-4.gif

2021 in review: lightning-fast video transcoding & playback and many new product features!

thumbnail_anne-sophie.jpg

anne-sophie.jpg

twitter-brands.svg

Twitter (Anne-Sophie)

Anne-Sophie Poupard

Following the launch of our [new visual identity](https://api.video/blog/product-updates/new-logo-same-mission-connecting-people-through-unique-video-experences/) a few weeks ago, we are now releasing **our new dashboard**: a complete visual and experience update providing easier access to manage your videos.

We have fully rebuilt the dashboard to feature a new, polished design. This redesign is not only about esthetics as we completely reviewed the navigation to provide a great user experience. 

The new dashboard has the same functionality that exists in the old design; all reimagined for the best usability. The new platform will improve the service we offer by increasing transparency, access to information and better management tools.

## What can you do?

* Access your API keys
* Access all the information related to your account and all the resources you need to use api.video (Clients, Tutorials, Docs, Demos, ...)
* Access and manage all your videos from your "Videos" section
* Upgrade to the Production environment and remove the watermark from your video content
* Monitor your usage
* Switch easily from a Sandbox to a Production environement to test without altering your Production.

large_dashboardapi.png

medium_dashboardapi.png

small_dashboardapi.png

thumbnail_dashboardapi.png

dashboardapi.png

## What is required from you?
You don't have to do anything, you already have access to the new dashboard: [Check it out](https://dashboard.api.video/register)

There are more great updates coming soon. It’s a really exciting time here at api.video and we can’t wait for you to see what’s next. 

If you have any questions, don't hesitate to contact us through the chat box inside the dashboard or through our [Community Forum](https://community.api.video)

Introducing our new dashboard

large_dahsboard.png

medium_dahsboard.png

small_dahsboard.png

thumbnail_dahsboard.png

dahsboard.png

The difference between good products and great products is "the magic" we can feel when we are using them.

## Good products
Good products get the job done - but still require a thought process to walk through the steps required to accomplish a task. They make us feel, as users, the succession of technical steps when we want to accomplish something.

If I want to record a video with my iPhone, I first open the Camera app, then slide to the video mode, press the red button to start my recording and press again to finish it. All the steps are clear to me and I'm not surprised with the result: I want to create a video → the way I use the tool allows me to create the video.

I don't have an emotional reaction, because while the design is great, it is not an effortless process. I don't wonder *'how did it do that?'* or feel like some type of magic occurred.

## Great products
Great products are different: **they provide me value from nowhere** and make the technical aspects of using the product disappear.

A perfect example of this is **Shazam**. We launch the app and it recognizes the music around us. We don’t even have to guess something like the singer or the lyrics. Instead, the app creates an audio fingerprint, requesting a database of tracks to find similar fingerprints until it matches the song for us. The process is effortless. This is “the magic."

Another example - **Google Photos**: we type a location, an object or a word in the search bar and the app will show us all pictures related to these terms while we have never created any metadata around our pictures. This is "the magic."

**Netflix**: we used to spend countless hours on obscure directories to find the right torrent for a movie, which is not a screen cam, without Korean subtitles embedded on the picture and in good quality. Now, we launch Netflix on all our screens, and the movie we want starts immediately, according to our settings (the audio we want, the subtitle we want). And it’s effortless. This is "the magic."

## Transcoding is key, but unimportant to users
We are living in a video-first world, but all of us don't have access to fast broadband and large screens.

Some of this is changing. With the rise of affordable electronics for video creation, people everywhere can make and upload videos, even if they don’t have the greatest internet connections. And with the advent of 5G, the ability to rapidly upload and transmit content will become available all over the World.

We used to live in a world where downloading and consuming content was what happened most, especially with mobile. But with the addition of 5G, now we are entering **an era of upload**.

As we join this new time, manufacturers keep promoting their proprietary video format, preventing us from sharing a video easily. This is why all video platforms [transcode](https://api.video/what-is/transcoding/) videos right after the upload. 

Transcoding is not something users want to think about. What users want is to **make their videos available worldwide in seconds**. They don’t want to think about whether to choose HLS or Dash or VP9 or H264. And they don’t want to sit staring at a transcoding progress bar for minutes. This is not magic. It’s slow and tedious.

What should happen is magic - a video is uploaded and an invisible, rapid process ensures that users can immediately show their brand new content to their audience. 

This is "the magic" that api.video strives to provide. We want to make transcoding quick and efficient, something you don’t ever need to think about.

## Reinventing the video transcoding pipeline
At api.video, we have worked hard to **reinvent our video transcoding pipeline** to deliver exceptional performances: 

* We put the transcoding process on EDGE servers, which means your videos get transcoded to a server close to you. This saves seconds you'd usually have to wait when using a traditional video platform with a centralized approach.
* Different versions of your video are transcoded by several servers at the same time to avoid the queue effect (waiting for transcoding to complete before starting another)

large_transcoding-time-and-host.png

medium_transcoding-time-and-host.png

small_transcoding-time-and-host.png

thumbnail_transcoding-time-and-host.png

transcoding-time-and-host.png

In the image above, five servers were used to generate the five qualities of a five minute video at the same time. 

* We also changed the way HLS assets are generated and written to storage to transfer the transcoded files in a few milliseconds

large_hls-encoding-time.png

medium_hls-encoding-time.png

small_hls-encoding-time.png

thumbnail_hls-encoding-time.png

hls-encoding-time.png

In the illustration above, the average 240p encoding duration for the five minute video was four seconds. However it took .53 seconds to send it to the storage system.

* We transcode the lowest quality first to let the video plyer start once this quality is ready, even if the highest qualities are still in progress.

By working and improving all the steps of the pipeline, the **five minute video** we used for this article was **ready to play anywhere in the world only four to five seconds after the upload ended**, and the high quality 720p version of the video was ready just eight seconds later.

That's a total of only 12.5 seconds after the upload was completed!

That’s a superb experience for all people who put a video online to share it.
This is our magic. 

large_encodingbench.jpg

medium_encodingbench.jpg

small_encodingbench.jpg

thumbnail_encodingbench.jpg

encoding-benchmark.jpg

## What's next?
We are super proud to make this [magic available to everyone](https://api.video/what-is/video-encoding/) as our [benchmark](https://api.video/platforms-benchmark/) (you can download the repo [here](https://github.com/apivideo/video-platform-bench) and the video used [here](https://test-videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_10MB.mp4)) demonstrates that we are increasing dramatically the Market performances to date.

Oh! And seconds are still too long: **we won't rest until we reach few milliseconds** :)

The magic behind great products

large_magicalproductpost.png

medium_magicalproductpost.png

small_magicalproductpost.png

thumbnail_magicalproductpost.png

magical-product-post.png

doug.jpg

Doug Twitter

Doug Sillars

At api.video, our goal is to make the process of working with video seamless. Principally, we do that via our APIs that make it really simple to encode, store, and deliver video worldwide. Another aspect, however, is that we need to make those APIs as accessible as possible via the tools that your company might already be using.

Today, we're pleased to announce our new app on the [Contentful marketplace](https://www.contentful.com/marketplace/app/api-video/). Our app makes it easy to bring video content to your websites and apps via Contentful and gives your entire team access to our powerful video APIs (check out our [API documentation](https://docs.api.video/reference)) right from the Contentful user interface.

In this post, we'll do a quick walkthrough on how to connect your api.video account to Contentful. 

All you'll need is:

1. A free Contentful account
2. An api.video API key (Get a free sandbox key [here](https://dashboard.api.video/))


## Installing the api.video app in Contentful


Log into your Contentful account and add the [api.video app](https://www.contentful.com/marketplace/app/api-video/) by clicking "Apps" and then "Manage apps" in the main nav bar.

Input your api.video API key first. You'll also notice that there is a list of your JSON objects are listed. The api.video app is meant to be connected to JSON object types in Contentful. If you don't see any objects listed, that's ok, we'll add a JSON object in the next step.

large_apivideoapp.jpg

medium_apivideoapp.jpg

small_apivideoapp.jpg

thumbnail_apivideoapp.jpg

apivideoapp.jpg

## Adding api.video to content models

In this section we'll add api.video to 2 different content models:

1. A new JSON object
2. Add it to the Component:Video Object


### A new JSON object

In the top menu, select "Content Model", and a new page will open with all the models/components in your app.  Choose the "Add content type" button on the top right to begin creating a new type:

large_contentful-headers.png

medium_contentful-headers.png

small_contentful-headers.png

thumbnail_contentful-headers.png

contentful-headers.png

large_namingthemodel.png

medium_namingthemodel.png

small_namingthemodel.png

thumbnail_namingthemodel.png

namingthemodel.png

The UI will walk you through adding fields. Click the blue button to add a field, and then add a JSON Object. You'll be asked to name the field - choose a name that reminds you that it is an api.video object that is being added.

Click the "Create and Configure" button, and under "Appearance" choose api.video:


large_modelconfiguration.png

medium_modelconfiguration.png

small_modelconfiguration.png

thumbnail_modelconfiguration.png

modelconfiguration.png

You may want to create a second field so that all items created with this object have a title.  Create a new field, text, Short text, and when you configure the item, click the "Entry title" button.  (If you do not add this step, every object you add will be named "Untitled" which is less than ideal.)


Your new component model now appears as an item to add when composing a page:


large_addingcomponent.png

medium_addingcomponent.png

small_addingcomponent.png

thumbnail_addingcomponent.png

addingcomponent.png

### Modifying the Component:video model

Contentful has a built in video model that you can add the api.video app to.  Let's walk through the steps to do that.

In the "Content Model" section, click on the "Component:Video" model.  This will give you a page that shows all the fields in the model.  By default, it has 2 fields, the title, and a YouTube Video Id.  We'll modify this so that you can still use a YouTube video Id, but you can also add an api.video object.

#### Add the api.video object

Click the "add field" button on the right. Add a JSON object, and name the field "apivideo" or another term that helps you remember where the videos will be stored.  Click the "Create and Configure" button, and then under Appearance, add the api.video app.


#### Edit the YouTube object

The Component:Video model is designed to only work with YouTube, and one of the settings is that the YouTube video Id is required.  We're making this model more flexible (YouTube AND api.video), so we need to remove this requirement.  Click the settings button, and under "Validation" you'll uncheck the "Required field" checkbox



large_checkbox-removal.png

medium_checkbox-removal.png

small_checkbox-removal.png

thumbnail_checkbox-removal.png

checkbox-removal.png

With these changes, we are now ready to save the Component:video model.


## Adding api.video videos to Contentful

The process is very similar - no matter which type of object you created in the last step.

### Using the Content section

In the top menu, choose content, and then pick the model you wish to use (in the screenshots, I've used the Component:Video model.


The title is 'My Awesome video', and I'm skipping the YouTube section - it's no longer required! With the api.video app, you can choose a video already uploaded to api.video ("select an existing video"), or upload a new video (descriptively named "upload a new video").



large_addingavideo.png

medium_addingavideo.png

small_addingavideo.png

thumbnail_addingavideo.png

addingavideo.png

If you choose an existing video, you can search through your api.video library by title, making video discovery easy.



large_videosearch.png

medium_videosearch.png

small_videosearch.png

thumbnail_videosearch.png

videosearch.png

Now just publish the content, and you've added the video for playback!

You can also add the content model in a page you are building and follow the same steps to add an api.video to your site.






large_screenshot-2021-10-08-at-14-18-13.png

medium_screenshot-2021-10-08-at-14-18-13.png

small_screenshot-2021-10-08-at-14-18-13.png

thumbnail_screenshot-2021-10-08-at-14-18-13.png

screenshot-2021-10-08-at-14-18-13.png

With the "upload a video" option - you'll get the option to upload a video from your local drive. The app will upload the video to api.video, and then show it in the window when it is ready to play.


## Conclusion

We're super excited to see what folks will build with api.video and Contentful. If you're looking for an easy way to integrate video into your application - give our integration a try with the [api.video app](https://www.contentful.com/marketplace/app/api-video/).

Questions? Our [documentation](https://docs.api.video/sdks/nocode/contentful) has more details.  Or, feel free to ask a question with the chat button, or check out our [community forum](https://community.api.video).

New Contentful integration: Adding video more easily

large_apivideo-contentful.png

medium_apivideo-contentful.png

small_apivideo-contentful.png

thumbnail_apivideo-contentful.png

apivideo-contentful.png

New Contentful integration: Adding video to your site just got even easier

A year ago, we looked at how [fast videos are encoded](https://api.video/blog/product-updates/video-encoding-rates-2h-2020/) at api.video. Over the past year, we've made huge upgrades to how we store and deliver video, as well as completely revamped our encoding infrastructure.  

In this post, we'll look at how quickly you can expect your video to be ready today, and we'll do some comparisons to our encoding speed 12 months ago.

## **TL;dr** Our encoding pipeline is a LOT faster. The median video encoding time is 20-40% faster over last year. We see even more impressive results at the 95th percentile where we are 48-63% faster year over year.  This means faster access to the videos uploaded for all of our customers and their users.

## Encoding process

When your video is uploaded to api.video, we take the video and create several different versions of the video HLS [adaptive bitrate streams](https://api.video/what-is/adaptive-bitrate-streaming/) and a [mp4](https://api.video/what-is/mp4/) version of the video.

The streams will have several different sizes: 240p, 360p, 480p, 720p, 1080p and 2160p.  We'll create versions up to the size of the video uploaded but no larger (so a 720p uploaded video will not have a 1080p or 2160p video).

The mp4 will be the size of the uploaded video (unless the video is 4K, where a 1080p mp4 version will be created.)

Based on data from June - September, we can count each encoded HLS version and determine the size of the original video:



large_encoded-video-size.png

medium_encoded-video-size.png

small_encoded-video-size.png

thumbnail_encoded-video-size.png

encoded-video-size.png



* 80% of videos uploaded are 720p or better, and 50% of all videos are either 1080p or 4K.


## Encoding time

As each version of the video is encoded, we measure the amount of time it took. 

There are two features that determine the encoding time - the size (dimensions) and duration of the video.

### video dimensions
A 240p video has 102,240 pixels in each frame (426x240).  A 1080p video has 2,073,600 pixels in each frame (1920x1080). With fewer pixels, the 240p video will generally encode faster than a 1080p video of the same duration.

### video duration

A video that is 1 minute long and encoded at 24 [frames per second](https://api.video/what-is/framerate-frames-per-second-fps/) will have 1,440 frames to be encoded. A 5 minute long video will have 7,200 frames, and will take longer to encode.

To try to make sense of this, we'll break down the video encoding times by the video's size, and create buckets of lengths, so that when we compare video encoding times, we are looking at videos of similar duration.

## Percentiles

Percentiles allow us to rank our data into even segments that add up to 100 - making comparison across different collections of data easier. The median value is the 50th percentile, or the value that falls exactly in the middle of the data set. In our charts, we'll show 25%, 50%, 75% (quartile data) for the encoding times.  We also will show the 90 and 95th percentiles, as these can give you an idea of the longer times a video might take to encode.



## Short video encoding (under 5 minutes)

Let's take a look at short videos - those that are under 5 minutes long.  we can calculate the tie it will take for each version to be created:



large_video-encode-times-2021.png

medium_video-encode-times-2021.png

small_video-encode-times-2021.png

thumbnail_video-encode-times-2021.png

video-encode-times-2021.png

The black line shows the 50th percentile - or when 50% of videos will have been encoded.  50% of videos will have a 240p version of the video ready in 7.8 seconds, a 720p version in 15.3 seconds, and a 4K in 35s.

95% of videos under 5 minutes will have the 720p video in 85s or less.  Larger sized videos take longer, and the 95th percentile for the 4K videos is 384s.

You can compare these numbers to the data from 2020, and they are very similar - within a few seconds of the data from a year ago.  We have a few tricks up our sleeve to make the next data set faster for these shorter videos.


## Longer video encoding

In order to compare against the data from a year ago, let's look at the encode times for videos 45-75 minutes long.  Note that the 2020 data omits the 4K data, as there were not enough 4k files at this duration to make a good analysis.  Here is the data at the 50th percentile:



large_50thpercentile-encode-data.png

medium_50thpercentile-encode-data.png

small_50thpercentile-encode-data.png

thumbnail_50thpercentile-encode-data.png

50thpercentile-encode-data.png

medium_screenshot-2021-09-27-at-19-57-03.png

small_screenshot-2021-09-27-at-19-57-03.png

thumbnail_screenshot-2021-09-27-at-19-57-03.png

screenshot-2021-09-27-at-19-57-03.png

The encoding for the median video is 21-38% faster, depending on the size of the video. A really nice improvement!

When reporting performance of our service, we want to monitor the 95th percentile - because we want EVERY video encoding to be fast.  In the chart below, we can see that difference between 2020 and 2021 is even larger at the 95% percentile than it is at the 50th:

large_95thpercentileencodingdata.png

medium_95thpercentileencodingdata.png

small_95thpercentileencodingdata.png

thumbnail_95thpercentileencodingdata.png

95thpercentileencodingdata.png

medium_screenshot-2021-09-27-at-19-59-28.png

small_screenshot-2021-09-27-at-19-59-28.png

thumbnail_screenshot-2021-09-27-at-19-59-28.png

screenshot-2021-09-27-at-19-59-28.png

At the 95th percentile, we see that all versions are ~50%-60% faster!  Longer videos that are uploaded to api.video are ready for playback significantly faster than a year ago. The changes to our encoding system is making a big difference in making videos available faster!


## Time as a continuum

We see that video encoding is faster, and we've looked at two data points - short and longer videos.  What can we learn about video encoding times over different periods of time?

Let's look at the 720p data.  720p is often a 'good enough' quality for playback - it may not be as good as 1080p or 4K, but you can start the playback, and most users will be satisfied with the video (and the 1080p and 4K videos will be ready right afterwards, if available).



720p encode times for different duration videos

large_720pencode-data.png

medium_720pencode-data.png

small_720pencode-data.png

thumbnail_720pencode-data.png

720pencode-data.png

This graph gives a good idea on how long you might have to wait after uploading a video before the 720p VOD file will be ready (assuming you know the duration).  For a very quick estimate - if you take the duration of your video in seconds, and divide by 2, over 95% of videos will be encoded by that time.


## Why wait?

api.video's encoding is continuing to improve, and we expect to see more jumps in encoding time in the near future.  Over the last year, we have improved the "waiting game" by introducing [webhooks](https://api.video/blog/endpoints/webhooks/) which will push to your server when each version of your video is encoded.



## Conclusion

Over the last year, we have made significant jumps in our encoding times - meaning that the videos your customers upload to api.video are ready for streaming playback faster than ever before.  We're not resting idly with this improvement - we expect our infrastructure and encoding pipelines to have further improvements as we continue to improve our service in the coming months!

If you haven't seen our lightning fast encoding yet, what are you waiting for - try it yourself by [signing up](https://dashboard.api.video/register) today!

api.video encoding times: 2H 2021 edition

large_screenshot-2021-10-05-at-09-22-57.png

medium_screenshot-2021-10-05-at-09-22-57.png

small_screenshot-2021-10-05-at-09-22-57.png

thumbnail_screenshot-2021-10-05-at-09-22-57.png

screenshot-2021-10-05-at-09-22-57.png

Today is the day - we are proud to officially launch our brand new visual identity!

As excited as we are to unveil our new look, this brand refresh symbolizes a lot more than just a fresh look. Our product, our features, our values, our mission are all reflected in this brand refresh.

A lot has happened over the past two years. It has been an exciting journey, and we have made tremendous progress in building a high-quality, high-performance product and assisting you in developing your own video products. Our recent achievements include: 

* New API Clients: [C#](https://docs.api.video/sdks/api-clients/apivideo-csharp-client), [Go](https://docs.api.video/sdks/api-clients/apivideo-go-client), [Python](https://docs.api.video/sdks/api-clients/apivideo-python-client), [Java](https://docs.api.video/sdks/api-clients/apivideo-java-client)
* [Live streaming](https://api.video/blog/product-updates/live-stream-webhooks-we-ll-tell-you-when-the-stream-starts/) and [VOD webhooks](https://api.video/blog/product-updates/new-feature-video-on-demand-webhooks/)

But one thing hasn’t changed: **our mission to make video accessible to every developer on the planet**.
 
Why the change?
Due to the high technical nature of our business and the complex nature of the industry we serve, it's crucial for us to keep our work simple and clear. Our brand should reflect this as well.
We created our previous logo at an early stage of api.video, when we had 10 people on the team with a goal to make the developers' life easier. The logo was dynamic, and colorful, but it was not representative of who we are and what we do: **video**!

Now we are 30 (and counting!) and our new look reflects the image of our company.

large_api-video-team.jpg

medium_api-video-team.jpg

small_api-video-team.jpg

thumbnail_api-video-team.jpg

api-video-team.jpg

First, we focused on what the current brand was representing and our mission: we are a tech company building an innovative, reliable, and developer-friendly video API. 

How?

Our logo lacked the main element of our product, and this was the first requirement of the brief.
We worked on a very popular symbol, used all over the Web: the play button. 

Yes, a simple triangle.

The new logo was created based on different key messages that combine a unique value proposition. As part of this logo we drew inspiration from the play button to represent video. Other references in this logo include:

* Technical: AV represents inputs and outputs that some of you may be familiar with from your old TVs
* Symbolic: the letters overlay represents the layering of the API
* Geeky: there is a reference to a classic video game (did you spot it?)

large_api-video-logo-process.png

medium_api-video-logo-process.png

small_api-video-logo-process.png

thumbnail_api-video-logo-process.png

api-video-logo-process.png

You shouldn't be constrained by your understanding of video codecs and protocols. Our goal is to enable you to build wildly innovative video experiences more quickly and easily than ever before.

New logo, same mission: Connecting people with video

large_blogimagenewbranding.png

blogimagenewbranding.png

New logo, same mission: Connecting people through unique video experiences

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