# HTML5 compatibility

> Understand which browsers and devices can run a PandaSuite HTML5 project, what limitations may appear depending on the features you use, and what to validate before release.

https://docs.pandasuite.com/essentials/web-publishing/html-5-compatibility/

**A PandaSuite project published in HTML5 is designed to run in a web browser on desktop, mobile, or tablet.**

Actual compatibility depends on three things:

1. the browser and its version;
2. the operating system and device;
3. the features enabled in your project.

In other words, a simple project mostly based on navigation, text, images, video, or audio will generally be more broadly compatible than a project relying on advanced browser or device capabilities.

## What “HTML5 compatible” means

When we talk about HTML5 compatibility, we mean that your project runs in a modern browser able to interpret the web technologies used by PandaSuite: visual rendering, audio/video, touch interactions, JavaScript, animations, and asset loading.

In practice, PandaSuite aims for broad compatibility across modern desktop and mobile browsers.

> **Info**
>
> A PandaSuite web project does not behave like a native app. Its behavior depends on the browser, its security rules, the permissions granted by the user, and sometimes the hosting context.

## Supported browsers and environments

Here are the minimum browser versions for a PandaSuite web app, whether it is published to the web or exported as a web package. Older versions are not supported.

| Browser                             | Minimum version                 | Technical points to watch                                                                                                                 |
| ----------------------------------- | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Chrome** (desktop and Android)    | Chrome 87+                      | Reference environment for validating rendering and interactions. On Android, check performance, permissions, and device-specific behavior |
| **Edge**                            | Edge 88+                        | Same engine as Chrome                                                                                                                     |
| **Firefox** (desktop and Android)   | Firefox 78+                     | Validate media, permissions, embedded integrations, and touch behavior                                                                    |
| **Safari** (macOS, iOS, and iPadOS) | Safari 14+ (iOS and iPadOS 14+) | Strong dependency on Apple rules for autoplay, audio, video, fullscreen, local storage, and iframes                                       |
| **Internet Explorer**               | Not supported                   | The web app does not start                                                                                                                |

Keep in mind:

- other Chromium-based browsers (Opera, Samsung Internet, Brave...) behave like the matching version of Chrome;
- for current delivery, always prefer recent browser versions;
- Chromium-based browsers often provide the most predictable behavior;
- Safari on iOS and macOS requires more validation around media, fullscreen, storage, and touch behavior;
- WebViews, LMS environments, and embedded browsers should always be tested in the real delivery environment.

## What affects compatibility

### Advanced web capabilities

Some behaviors depend heavily on the browser being used, including:

- service workers and PWA behavior;
- media playback with autoplay or automatically triggered audio;
- fullscreen mode;
- local storage, caching, and offline behavior;
- the system WebView on mobile.

### Device permissions and hardware

Other use cases depend on the device itself and on user permissions, for example:

- camera;
- geolocation;
- microphone;
- sensors or device-specific APIs.

So a compatible browser alone does not guarantee that every feature of your project will be available in every situation.

### Hosting context

Behavior can also vary depending on whether your project is:

- hosted on PandaSuite;
- self-hosted on your own server;
- launched locally from a web package;
- embedded in an LMS or inside an iframe.

Some browser security restrictions appear more frequently in local or constrained embedding environments.

## Special case: PWA and service workers

If you enable service workers or PWA-related features, compatibility becomes more specific. A project may still remain accessible as a regular web app while losing some advanced capabilities depending on the browser in use.

See the dedicated article: [Activate the service workers](https://docs.pandasuite.com/essentials/web-publishing/activate-the-service-workers/).

## Recommendations before release

Before publishing your HTML5 project, we recommend testing at least:

- one Chromium-based desktop browser;
- Safari if your audience uses Apple devices;
- one iOS mobile browser;
- one Android mobile browser;
- the critical flows for navigation, loading, media playback, and interactions.

Prioritize checking:

- responsive rendering;
- loading performance;
- videos, audio, and animations;
- browser permissions;
- offline behavior if you use service workers;
- LMS integration if you export as SCORM or CMI5.

> **Warning**
>
> If your project is intended for a constrained environment such as an LMS, an enterprise browser, or an older device, always test on the actual devices and browsers used by your audience.

## Go further

- [Publish to the Web](https://docs.pandasuite.com/essentials/web-publishing/publish-to-the-web/)
- [Export a web package](https://docs.pandasuite.com/essentials/web-publishing/export-a-zip-file/)
- [Activate the service workers](https://docs.pandasuite.com/essentials/web-publishing/activate-the-service-workers/)
- [Embed into a website](https://docs.pandasuite.com/essentials/web-publishing/embed-into-a-website/)