Qt for WebAssembly
Qt for WebAssembly makes it possible to build Qt applications as WebAssembly modules in order to target Web browsers.
Qt for WebAssembly is currently in development. A second tech preview release is scheduled for release with Qt 5.12.0.
The main development tracking bug is https://bugreports.qt.io/browse/QTBUG-63917.
Getting the code
The sources can be downloaded from your Qt Account, in the Downloads section. For the latest revision of the code, you can also check it out from our git repositories directly: http://code.qt.io/cgit/qt/qt5.git/
Building Qt
Requirements: Emscripten (known-good version: 1.38.1)
Supported host dev platforms: Linux, macOS, Windows Subsystem for Linux
./configure -xplatform wasm-emscripten -nomake examples
make
Building and running applications
/path/to/qmake && make
Start a web server (e.g. "python -m SimpleHTTPServer"), open e.g. localhost:8000/appname.html in a web browser. We test on Chrome, Firefox, and Safari (all desktop). Firefox (nightly) currently has the most performant wasm compiler, and is recommended for dev work.
You can also use:
/path/to/emscripten/emrun --browser=firefox appname.html
Note: If you are using Firefox, you can use CTRL+SHIFT+K to open the debug console.
Known issues and platform notes
- Supported development host systems: Linux and MacOS, and Windows Subsystem for Linux.
- Supported browsers: We develop and test mainly on desktop systems. Tested browsers include Chrome, Safari, Opera and Firefox. Some mobile testing is done on Android and iOS devices. Safari on iOS currently failing to load Qt applications with an "out of executable memory" error.
- Due to disabled threading support in WebAssembly at the moment, the configure string above will build Qt with no threading support. Applications that relies on threading may not work.
- Nested event loops are not supported. Applications should not call e.g. QDialog::exec() or create a new QEventLoop object.
- Qt renders application content to a canvas element, and does not use (other) native DOM elements. This means accessibility (screen readers) are not supported and that text inputs won't trigger virtual keyboards.
- WebGL is required, even for applications which do not use OpenGL themselves. All relevant browsers support WebGL, but note that some browsers blacklist certain older GPUs. The Qt loader will detect this and display an error message.
- Applications do not have access to system fonts. Font files must be distributed with the application, for example in Qt resources. Qt for WebAssembly itself embeds one such font.
- High-DPI and scaling: High-DPI rendering is supported, and so is setting the overall UI visual size using the browser zoom feature. Browser font size (and type) settings have no effect on Qt applications.
- Network access: The web sandbox limits network access to a subset of what is available for native apps.
- QNetworkAccessManager http requests to the web page origin server, or to a server which supports CORS.
- QWebScoket connections to any host.
- TCP and UDP socked tunneling using over WebSockets using a websockify server [implemented by Emscripten, not tested]
- Clipboard support: The application clipboard is currently not integrated with the system clipboard.
- On macOS, there may be artifacts of uninitialized graphics memory on some Qt Quick Controls 2 components, such as checkboxes.
Expected footprint (download size): Wasm modules as produced by the compiler can be large, but compress well.
| Example | gzip | brotli |
|---|---|---|
| helloglwindow (QtCore + QtGui) | 2.8M | 2.1M |
| wiggly widget (QtCore + QtGui + QtWidgets) | 4.3M | 3.2M |
| SensorTag (QtCore + QtGui + QtWidgets + QtQuick + QtCharts) | 8.6M | 6.3M |
Compression is typically handled on the web server side, using standard compression features: the server compresses automatically or picks up pre-compressed versions of the files. There's generally no need to have special handling of wasm files.