Need help with LiTr?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

333 Stars 56 Forks BSD 2-Clause "Simplified" License 167 Commits 32 Opened issues


Lightweight hardware accelerated video/audio transcoder for Android.

Services available


Need anything else?

Contributors list


Build Status

LiTr (pronounced "lai-tr") is a lightweight video/audio transformation tool which supports transcoding video and audio tracks with optional frame modification.

In its current iteration LiTr supports: - changing resolution and/or bitrate of a video track(s) - changing bitrate of an audio track(s) - overlaying bitmap watermark onto video track(s) - applying different effects (brightness/contrast, saturation/hue, blur, etc.) to video pixels - including/excluding tracks, which allows muxing/demuxing tracks - transforming tracks individually (e.g. apply overlay to one video track, but not the other) - positioning source video frame arbitrarily onto target video frame - trimming video/audio - ability to create "empty" video, or a video out of single image

By default, LiTr uses Android MediaCodec stack for hardware accelerated decoding/encoding and OpenGL for rendering. It also uses MediaExtractor and MediaMuxer to read/write media.

Getting Started

Simply grab via Gradle:

 implementation ''

...or Maven:

How to Transform a Video

First, instantiate

with a
that can access
s you will be using for input and output. Most commonly, that will be an application context.
MediaTransformer mediaTransformer = new MediaTransformer(getApplicationContext());

Then simply call

method to transform your video:

Few notable things related to transformation: - make sure to provide a unique

, it will be used when calling back on a listener, or needed when cancelling an ongoing transformation - target formats will be applied to all tracks of that type, non video or audio tracks will be copied "as is" - passing
target format means that you don't want to modify track(s) of that type - transformation is performed asynchronously, listener will be called with any transformation progress or state changes - by default listener callbacks happen on a UI thread, it is safe to update UI in listener implementation. It is also possible to have them on a non-UI transformation thread, for example, if any "heavy" works needs to be done in listener implementation. - if you want to modify video frames, pass in a list of
s in
, which will be applied in order - client can call
multiple times, to queue transformation requests - video will be written into MP4 container, we recommend using H.264 ("video/avc" MIME type) for target encoding - progress update granularity is 100 by default, to match percentage, and can be set in
- media can be optionally trimmed by specifying a

Ongoing transformation can be cancelled by calling

with its

When you no longer need

, please release it. Note that
instance becomes unusable after you release it, you will have to instantiate a new one.

Handling errors

When transformation fails, exception is not thrown, but rather provided in

callback. LiTr defines its own exceptions for different scenarios. For API >= 23, LiTr exception will also contain
as a cause.

Reporting statistics

When possible, transformation statistics will be provided in listener callbacks. Statistics include source and target track formats, codecs used and transformation result and time for each track.

Beyond Defaults

By default, LiTr uses Android MediaCodec stack to do all media work, and OpenGl for rendering. But this is not set in stone.

At high level, LiTr breaks down transformation into five essential steps: - reading encoded frame from source container - decoding source frame - rendering a source frame onto target frame, optionally modifying it (for example, overlaying a bitmap) - encoding target frame - writing encoded target frame into target container

Each transformation step is performed by a component. Each component is abstracted as an interface: -


When using your own component implementations, make sure that output of a component matches the expected input of a next component. For example, if you are using a custom

(AV1?), make sure it accepts whatever frame format
produces (
) and outputs what
expects as an input.

Custom components can be used in

s in below "low level" transform method:
         List trackTransforms,

This API allows defining components and parameters per media track, thus allowing track based operations, such as muxing/demuxing tracks, transcoding different tracks differently, changing track order, etc.

Using Filters

You can use custom filters to modify video frames. Write your own in OpenGL as an implementation of

interface when you need to make extra draw operations which do not need access to source video frames. If you need to change how source video frame is rendered onto a target video frame, implement
interface. There are several filters already available from "filter pack" library, which is available via Gradle:

LiTr now has 40 new GPU accelerated video filters ported from Mp4Composer-android and android-gpuimage projects. You can also create your own filter simply by configuring VideoFrameRenderFilter with your custom shader, with no extra coding!

 implementation ''

...or Maven:

You can pass in a list of filters when transforming a video. Keep in mind that filters will be applied in the order they are in the list, so ordering matters.

Using in Tests

is very intentionally not a singleton, to allow easy mocking of it in unit tests. There is also
for UI tests, which can synchronously "play back" a sequence of listener callbacks.


Core business logic in LiTr is well covered by unit tests. LiTr is designed to use dependency injection pattern, which makes it very easy to write JVM tests with mocked dependencies. We use Mockito framework for mocking.

Demo App

LiTr comes with pretty useful demo app, which lets you transcode video/audio tracks with different parameters, in addition to providing sample code.


Please read for details on our code of conduct, and the process for submitting pull requests to us.


For the versions available, see the tags on this repository.


You can use snapshot builds to test the latest unreleased changes. A new snapshot is published after every merge to the main branch by the Deploy Snapshot Github Action workflow.

Just add the Sonatype snapshot repository to your Gradle scripts:

repositories {
    maven {
        url ""

You can find the latest snapshot version to use in the file.


  • Izzat Bahadirov - Initial work - LiTr

See also the list of contributors who participated in this project.


This project is licensed under the BSD 2-Clause License - see the LICENSE file for details


  • A huge thank you to ypresto for his pioneering work on android-transcoder project, which was an inspiration and heavy influence on LiTr
  • A special thank you to MasayukiSuda for his work on Mp4Composer-android project, whose filters now power LiTr, and for his work on ExoPlayerFilter project which was a foundation for filter preview functionality in LiTr.
  • A special thank you to android-gpuimage project for amazing filter collection, which is now being migrated into LiTr
  • A thank you to Google's AOSP CTS team for writing Surface to Surface rendering implementation in OpenGL, which became a foundation for GlRenderer in LiTr
  • A shout out to my awesome colleagues Amita Sahasrabudhe, Long Peng and Keerthi Korrapati for contributions and code reviews
  • A shout out to my colleague Vidhya Pandurangan for prototyping video trimming, which now became a feature
  • A shout out to our designer Mauroof Ahmed for giving LiTr a visual identity
  • A shout out to PurpleBooth for very useful template
  • A shout out to Ma7moudHatem for his invaluable contributions to LiTr

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.