We are aware of the recently disclosed PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) and can confirm FROALA is not impacted by these vulnerabilities.

0
Days
00
Hours
00
Minutes
00
Seconds
x
Skip to content
Froala Documentation

Browser and Framework Support

This page explains which browsers, frameworks and server SDKs Froala supports today.

Browser Support

Froala supports a browser version only while the browser’s maker still supports it. For each browser, we support the current major version and the one before it.

“Supported” means we actively test the editor in that browser and fix bugs reported for it.

Active Support

We test the editor in the current and previous major version of each browser listed below. If you find an issue in any of them, please report it as a bug in our Github repository.

  • Chrome
  • Firefox
  • Safari
  • Opera
  • Edge

⏳Coming in Froala 6

Nothing changes in Froala 5.x. These updates apply from Froala 6:

  • Internet Explorer 11 will no longer be supported.
  • iOS and Android support will follow the current and previous major versions, instead of fixed minimum versions.
  • Firefox ESR and mobile WebViews will be added to the supported list.

Unsupported Browsers

We don’t support pre-release browser versions, such as beta, dev or canary builds. If you find a bug in one of them, please report it to the browser’s maker.

Froala may also run in older browser versions not listed above, but we don’t test it there and usually don’t fix bugs that appear only in those versions.

How we test

Froala is tested automatically in every supported browser using unit tests. We use BrowserStack to test on many browser versions and platforms. Small differences can still appear between browsers, because each browser handles some things in its own way.

Only the latest Froala release receives bug fixes and new features. If you find a bug in an older version, please upgrade to the latest release first to check whether it’s already fixed.

Found a bug in a supported browser? Report it on our GitHub repository.

Fonts not Showing in Firefox

If you open the examples straight from your computer (a file:/// address) instead of from a web server, the editor icons might not show up in Firefox. This is because Firefox blocks web fonts loaded from folders outside the page’s own folder.

To fix this, type about:config in the Firefox address bar and change security.fileuri.strict_origin_policy from true to false.

Frameworks and Server SDKs Support

Framework integrations connect the editor to a front-end framework or CMS. Server SDKs help your server handle things like image and file uploads.

⏳Coming in Froala 6

Nothing changes in Froala 5.x. These updates apply from Froala 6:

  • Eleven older framework integrations will be retired, including Ember, Symfony, CakePHP, Yii 2, Craft CMS 3 and Meteor.
  • All supported integrations and server SDKs will be updated to the latest versions of their frameworks and languages.

Active Support

Froala currently supports 18 frameworks and 6 SDKs.

Integrations retiring in Froala 6

These integrations will keep working with Froala 5.x, but they won’t be included or updated in Froala 6.

  • Aurelia
  • CakePHP
  • Craft CMS 3
  • Ember
  • Knockout
  • Meteor
  • Symfony
  • Yii 2
  • AngularJS (Angular 1)
  • Laravel Nova

Using an integration that’s being retired?

You have three options:

  • Stay on the latest Froala 5.x release, which still includes your integration.
  • Use the core Froala editor directly. Install it with npm install froala-editor and add it to your app without the integration package.
  • Talk to our team. Contact Sales

Do you think we can improve this article? Let us know.