Using MobileFFmpeg in Commercial Applications

It is possible to use MobileFFmpeg in commercial applications but there are licensing conditions that must be met depending on the version used.

First of all, please note that IOS libraries are static and Android libraries are dynamic/shared.

• Dynamic LGPL libraries of MobileFFmpeg can be used in a commercial applications. In this using scheme, commercial application will have its own license and MobileFFmpeg will be licensed under LGPL. The most important part of this scheme is, users of commercial application should be able to and allowed to replace MobileFFmpeg library with another version. It can be hard to achieve that in IOS App Store and Google Play Store, so be aware of this situation.

• When static LGPL libraries are used there are two options. Either publishing commercial application source code under LGPL or providing commercial application in an object (not necessarily source) format, so that a user has the opportunity to modify the LGPL library and relink the commercial application. Most developers find it hard to provide an application in an object format to allow relinking so they prefer providing source code of their application.

• If GPL libraries are used, either dynamic or static, commercial application will be licensed under GPL, all conditions defined by GPL must be met. This means you must make the source code available to the users of your commercial application as described in the GPL, and they must be allowed to redistribute and modify it as described in the GPL.

Note: IOS universal static binaries are prebuilt binaries with -ios-static-universal postfix or binaries built by providing --static flag to ios.sh build script.