# Browser Compatibility for video-use: Requirements and Platform Support > Understand video-use browser compatibility. Discover requirements and platform support for seamless video playback across modern browsers when using Browser Use Cloud or Box. - Repository: [Browser Use/video-use](https://github.com/browser-use/video-use) - Tags: getting-started - Published: 2026-07-10 --- **video-use is a server-side Python package that requires no specific browser client, supporting any modern web browser (Chrome ≥89, Firefox ≥86, Safari ≥14, Edge ≥89) only when accessed through Browser Use Cloud or Browser Use Box interfaces.** The **browser-use/video-use** repository provides an AI-powered video editing framework that runs entirely on the backend. Because the core logic executes in Python rather than the browser, browser compatibility for video-use depends entirely on how you access the tool—either through the hosted Browser Use Cloud platform or a self-hosted Browser Use Box instance. ## Backend Architecture and Browser Independence **video-use** operates as a pure-Python package designed to run via Claude Code, Codex, Hermes, or similar agent environments. The repository contains no front-end JavaScript or HTML; all heavy lifting—including video transcription, packing, and rendering—occurs server-side through modules like [`helpers/transcribe.py`](https://github.com/browser-use/video-use/blob/main/helpers/transcribe.py) and [`helpers/render.py`](https://github.com/browser-use/video-use/blob/main/helpers/render.py). As noted in [`SKILL.md`](https://github.com/browser-use/video-use/blob/main/SKILL.md), the editing workflow executes Python commands that interface with system libraries like `ffmpeg`. This architecture means the client browser serves only as a display mechanism for chat interfaces, while the actual processing happens independently on the server. ## Browser Use Cloud Compatibility When using **Browser Use Cloud** (the hosted agent platform at `cloud.browser-use.com`), the web interface requires only standard modern browser capabilities: - **Chrome**: version 89 or later - **Edge**: version 89 or later - **Firefox**: version 86 or later - **Safari**: version 14 or later The cloud UI is a standard HTML/JavaScript application that requires no special plugins, extensions, or experimental APIs. As documented in [`README.md`](https://github.com/browser-use/video-use/blob/main/README.md), the cloud demo links point to standard web applications that function across all mainstream browsers supporting contemporary web standards. ## Browser Use Box Self-Hosting Requirements For **Browser Use Box** (the self-hosted agent platform), browser compatibility mirrors the cloud service exactly. Since the Box serves a simple webpage to load the UI, any browser capable of rendering standard HTML5 and JavaScript will suffice. The [`install.md`](https://github.com/browser-use/video-use/blob/main/install.md) file provides setup instructions for running the server locally, with the browser merely displaying the interface while Python code executes on the host machine. ## Server-Side Dependencies vs Browser Requirements While client browsers need only modern web standards, the server running **video-use** has specific requirements documented in [`install.md`](https://github.com/browser-use/video-use/blob/main/install.md): - **Python 3.10+** for running the core package - **ffmpeg** installation for video processing - **ElevenLabs API key** for text-to-speech features These dependencies operate entirely on the backend. For example, invoking `video_use.edit_folder()` processes video files using [`helpers/render.py`](https://github.com/browser-use/video-use/blob/main/helpers/render.py) and [`helpers/transcribe.py`](https://github.com/browser-use/video-use/blob/main/helpers/transcribe.py) on the server, regardless of which browser (if any) initiated the request. ```python # Example: Server-side execution independent of browser # Based on usage patterns in SKILL.md and helpers modules import video_use # Process raw footage using backend ffmpeg and transcription video_use.edit_folder("/path/to/my/videos") ``` ## Summary - **video-use** requires no browser-specific logic because it runs as a Python backend service - **Browser Use Cloud** supports Chrome ≥89, Edge ≥89, Firefox ≥86, and Safari ≥14 without plugins - **Browser Use Box** (self-hosted) inherits the same browser compatibility as the cloud platform - Server requirements (Python 3.10+, ffmpeg) are documented in [`install.md`](https://github.com/browser-use/video-use/blob/main/install.md) and [`README.md`](https://github.com/browser-use/video-use/blob/main/README.md) - Client browsers only display the UI; actual video processing occurs in `helpers/*.py` modules on the server ## Frequently Asked Questions ### Does video-use work on mobile browsers? Yes, **video-use** supports mobile browsers when accessed through Browser Use Cloud or Browser Use Box, provided the mobile browser meets modern web standards (iOS Safari 14+, Chrome Mobile 89+). However, because the tool performs heavy video processing server-side using `ffmpeg` in the `helpers/` directory, performance depends on server resources, not mobile device capabilities. ### What are the exact browser version requirements for Browser Use Cloud? According to the platform specifications referenced in [`README.md`](https://github.com/browser-use/video-use/blob/main/README.md), Browser Use Cloud requires Chrome 89+, Edge 89+, Firefox 86+, or Safari 14+. These versions support the necessary Web APIs and security standards for the hosted agent interface. No additional browser extensions or special configurations are required. ### Can I run video-use without using a browser at all? Yes, **video-use** functions as a standalone Python package that can execute entirely from the command line or within agent environments like Claude Code. The [`SKILL.md`](https://github.com/browser-use/video-use/blob/main/SKILL.md) file documents production rules for LLM-driven editing workflows that run via Python imports without any browser component, using only the `helpers/` modules and local `ffmpeg` installation. ### Does video-use require browser plugins or extensions? No, **video-use** requires no browser plugins, extensions, or experimental features. The Browser Use Cloud and Box interfaces operate as standard web applications. All video processing capabilities—transcription, rendering, and packing—reside in server-side Python files like [`helpers/transcribe.py`](https://github.com/browser-use/video-use/blob/main/helpers/transcribe.py) and [`helpers/render.py`](https://github.com/browser-use/video-use/blob/main/helpers/render.py), eliminating the need for client-side browser plugins.