Platform Layers

Relevant source files

• core/profiling/SCsub
• core/profiling/profiling.cpp
• core/profiling/profiling.h
• core/profiling/profiling_builders.py
• doc/classes/DisplayServer.xml
• misc/dist/html/editor.html
• misc/dist/html/full-size.html
• misc/dist/html/manifest.json
• misc/dist/html/offline-export.html
• misc/dist/html/offline.html
• misc/dist/html/service-worker.js
• misc/scripts/install_perfetto.py
• platform/android/display_server_android.cpp
• platform/android/display_server_android.h
• platform/android/java_godot_io_wrapper.cpp
• platform/android/java_godot_io_wrapper.h
• platform/android/java_godot_lib_jni.cpp
• platform/android/java_godot_lib_jni.h
• platform/android/java_godot_wrapper.cpp
• platform/android/java_godot_wrapper.h
• platform/android/os_android.cpp
• platform/android/os_android.h
• platform/ios/display_server_ios.h
• platform/ios/display_server_ios.mm
• platform/ios/main_ios.mm
• platform/ios/os_ios.h
• platform/ios/os_ios.mm
• platform/linuxbsd/godot_linuxbsd.cpp
• platform/linuxbsd/wayland/SCsub
• platform/linuxbsd/wayland/display_server_wayland.cpp
• platform/linuxbsd/wayland/display_server_wayland.h
• platform/linuxbsd/wayland/godot-embedding-compositor.xml
• platform/linuxbsd/wayland/wayland_embedder.cpp
• platform/linuxbsd/wayland/wayland_embedder.h
• platform/linuxbsd/wayland/wayland_thread.cpp
• platform/linuxbsd/wayland/wayland_thread.h
• platform/linuxbsd/x11/display_server_x11.cpp
• platform/linuxbsd/x11/display_server_x11.h
• platform/macos/display_server_macos.h
• platform/macos/display_server_macos.mm
• platform/macos/godot_main_macos.mm
• platform/macos/godot_window_delegate.mm
• platform/macos/os_macos.h
• platform/macos/os_macos.mm
• platform/visionos/main_visionos.mm
• platform/web/SCsub
• platform/web/display_server_web.cpp
• platform/web/display_server_web.h
• platform/web/emscripten_helpers.py
• platform/web/eslint.config.cjs
• platform/web/godot_js.h
• platform/web/godot_webgl2.h
• platform/web/js/engine/config.js
• platform/web/js/engine/engine.js
• platform/web/js/engine/features.js
• platform/web/js/libs/library_godot_display.js
• platform/web/js/libs/library_godot_input.js
• platform/web/js/libs/library_godot_os.js
• platform/web/js/libs/library_godot_webgl2.externs.js
• platform/web/js/libs/library_godot_webgl2.js
• platform/web/net_socket_web.h
• platform/web/os_web.cpp
• platform/web/os_web.h
• platform/web/package-lock.json
• platform/web/package.json
• platform/web/serve.py
• platform/web/web_main.cpp
• platform/windows/display_server_windows.cpp
• platform/windows/display_server_windows.h
• platform/windows/godot_windows.cpp

The Platform Layer in Godot provides the essential abstraction between the engine's core logic and the underlying Operating System (OS) and hardware. This layer handles window management, input events, file system access, and specialized hardware integrations like XR.

Godot utilizes a specialized inheritance structure where the OS class provides a generic interface, and platform-specific implementations (e.g., OS_Android, OS_MacOS, OS_Web) handle the concrete logic for each environment.

Architecture Overview

The platform layer bridges the "Godot World" (Main Loop, Servers) to the "Host World" (Android Activity, Web Browser, macOS Window). Each platform implements a DisplayServer to manage graphical surfaces and a platform-specific OS class for system-level services.

Core Abstractions

• OS: Manages process execution, file paths, and system alerts platform/android/os_android.h43-171 platform/macos/os_macos.h42-160
• DisplayServer: Handles windowing, mouse/keyboard input, and screen management platform/android/display_server_android.h43-106 platform/windows/display_server_windows.h195-210
• AudioDriver: Interfaces with system audio APIs like OpenSL (Android) platform/android/os_android.h62 or XAudio2 (Windows) platform/windows/display_server_windows.h42-44

Platform Integration Diagram

The following diagram maps engine-level abstractions to their concrete Android and macOS implementations.

Sources: platform/android/os_android.h43-110 platform/android/java_godot_lib_jni.cpp165-186 platform/macos/os_macos.mm31-50 platform/macos/display_server_macos.h71-100

---

Android Platform

The Android implementation relies heavily on a JNI (Java Native Interface) bridge. The engine is initialized through Java_org_godotengine_godot_GodotLib_initialize, which sets up the OS_Android instance and connects it to the Java-side wrappers platform/android/java_godot_lib_jni.cpp165-186

• JNI Bridge: Managed via java_godot_lib_jni.cpp, facilitating communication between C++ and the Java Virtual Machine. The GodotJavaWrapper class platform/android/java_godot_wrapper.h43 provides C++ access to Java methods, while GodotIOJavaWrapper platform/android/java_godot_io_wrapper.h34 handles I/O specific calls.
• Input: Handled by AndroidInputHandler, converting Android motion events into Godot InputEvent types platform/android/java_godot_lib_jni.cpp33
• File Access: Specialized wrappers like FileAccessAndroid and DirAccessJAndroid allow Godot to read from APK assets and internal storage platform/android/os_android.cpp107-135

For details, see Android Platform.

Sources: platform/android/os_android.cpp107-135 platform/android/java_godot_lib_jni.cpp165-186 platform/android/display_server_android.cpp75-105

---

Web Platform

The Web platform targets WebAssembly (WASM) via the Emscripten toolchain. It translates Godot's C++ calls into JavaScript browser APIs.

• Execution: The engine is started via the Engine class in engine.js which manages the WASM module lifecycle. The OS_Web class platform/web/os_web.h35 provides the core OS abstraction.
• Display: DisplayServerWeb interfaces with the HTML5 Canvas and handles DOM events (keys, mouse, touch) platform/web/display_server_web.cpp67-185
• Shell: Uses HTML templates like editor.html or full-size.html to define the environment where the canvas and status overlays reside misc/dist/html/full-size.html96-108

For details, see Web Platform.

Sources: platform/web/display_server_web.cpp31-185 platform/web/os_web.h35 misc/dist/html/full-size.html112-214

---

XR & OpenXR

The XR system is integrated into the platform layer through the XRServer and the OpenXR module. It provides a unified interface for VR/AR hardware using the OpenXR standard.

• OpenXRAPI: The central singleton managing the OpenXR instance (XrInstance), session state (XrSession), and swapchains.
• Action Map: Maps hardware interaction profiles to engine-level actions.
• Extensions: A wrapper system (OpenXRExtensionWrapper) allows Godot to support vendor-specific features like Hand Tracking or Foveated Rendering.

XR Interface Hierarchy

This diagram bridges the engine's generic XR abstractions to the concrete OpenXR implementation.

Sources: platform/android/java_godot_lib_jni.cpp58-60 platform/android/display_server_android.cpp44-51

For details, see XR & OpenXR.

---

Platform-Specific Implementation Summary

Platform	OS Implementation	Display Server	Entry Point / Bridge
Android	OS_Android platform/android/os_android.h43	DisplayServerAndroid platform/android/display_server_android.h43	java_godot_lib_jni.cpp platform/android/java_godot_lib_jni.cpp165
Web	OS_Web platform/web/os_web.h35	DisplayServerWeb platform/web/display_server_web.cpp31	engine.js / WASM
macOS	OS_MacOS platform/macos/os_macos.h42	DisplayServerMacOS platform/macos/display_server_macos.h71	godot_main_macos.mm
Windows	OS_Windows	DisplayServerWindows platform/windows/display_server_windows.h195	godot_windows.cpp
Linux/BSD	OS_Unix	DisplayServerX11 / DisplayServerWayland	godot_linuxbsd.cpp

Sources: platform/android/os_android.h43 platform/android/display_server_android.h43 platform/macos/display_server_macos.h71 platform/web/display_server_web.cpp31 platform/windows/display_server_windows.h195 platform/linuxbsd/x11/display_server_x11.cpp181 platform/linuxbsd/wayland/display_server_wayland.cpp126