Webgl Online Tutorials

WebGL 1.0 is based on OpenGL ES 2.0 and provides an API for 3D graphics. It uses the HTML5 canvas element and is accessed using Document Object Model (DOM) interfaces.

WebGL 2.0 is based on OpenGL ES 3.0. It guarantees the availability of many optional extensions of WebGL 1.0, and exposes new APIs. Automatic memory management is provided implicitly by JavaScript.

Like OpenGL ES 2.0, WebGL lacks the fixed-function APIs introduced in OpenGL 1.0 and deprecated in OpenGL 3.0. This functionality, if required, has to be implemented by the developer using shader code and JavaScript.

Shaders in WebGL are written in GLSL and passed to the WebGL API as text strings. The WebGL implementation compiles these strings to GPU code. This code is executed for each vertex sent through the API and for each pixel rasterized to the screen.

WebGL evolved out of the Canvas 3D experiments started by Vladimir Vukićević at Mozilla. Vukićević first demonstrated a Canvas 3D prototype in 2006. By the end of 2007, both Mozilla and Opera had made their own separate implementations.

In early 2009, the non-profit technology consortium Khronos Group started the WebGL Working Group, with initial participation from Apple, Google, Mozilla, Opera, and others. Version 1.0 of the WebGL specification was released March 2011. As of March 2012, the chair of the working group is Ken Russell.

An early application of WebGL was Zygote Body. In November 2012 Autodesk announced that they ported most of their applications to the cloud running on local WebGL clients. These applications included Fusion 360 and AutoCAD 360.

Development of the WebGL 2 specification started in 2013 and finished in January 2017. The specification is based on OpenGL ES 3.0. First implementations are in Firefox 51, Chrome 56 and Opera 43.

Almost Native Graphics Layer Engine edit

Almost Native Graphics Layer Engine (ANGLE) is an open source graphic engine which implements WebGL 1.0 (2.0 which closely conforms to ES 3.0) and OpenGL ES 2.0 and 3.0 standards. It is a default backend for both Google Chrome and Mozilla Firefox on Windows platforms and works by translating WebGL and OpenGL calls to available platform-specific APIs. ANGLE currently provides access to OpenGL ES 2.0 and 3.0 to desktop OpenGL, OpenGL ES, Direct3D 9, and Direct3D 11 APIs. ″ Chrome uses ANGLE for all graphics rendering on Windows, including the accelerated Canvas2D implementation and the Native Client sandbox environment.″

WebGL is widely supported by modern browsers. However, its availability depends on other factors, too, like whether the GPU supports it. The official WebGL website offers a simple test page. More detailed information (like what renderer the browser uses, and what extensions are available) can be found at third-party websites.

Desktop browsers edit

• Google Chrome – WebGL 1.0 has been enabled on all platforms that have a capable graphics card with updated drivers since version 9, released in February 2011. By default on Windows, Chrome uses the ANGLE (Almost Native Graphics Layer Engine) renderer to translate OpenGL ES to Direct X 9.0c or 11.0, which have better driver support. However, on Linux and Mac OS X, the default renderer is OpenGL. It is also possible to force OpenGL as the renderer on Windows. Since September 2013, Chrome also has a newer Direct3D 11 renderer, which requires a newer graphics card. Chrome 56+ supports WebGL 2.0.
• Firefox – WebGL 1.0 has been enabled on all platforms that have a capable graphics card with updated drivers since version 4.0. Since 2013 Firefox also uses DirectX on the Windows platform via ANGLE. Firefox 51+ supports WebGL 2.0.
• Safari – Safari 6.0 and newer versions installed on OS X Mountain Lion, Mac OS X Lion and Safari 5.1 on Mac OS X Snow Leopard implemented support for WebGL 1.0, which was disabled by default before Safari 8.0. Safari version 12 (available in MacOS Mojave) has available support for WebGL 2.0 as an "Experimental" feature. Safari 15 enables WebGL 2.0 for all users.^[33]
• Opera – WebGL 1.0 has been implemented in Opera 11 and 12, but was disabled by default in 2014.^[34][35] Opera 43+ supports WebGL 2.0.
• Internet Explorer – WebGL 1.0 is partially supported in Internet Explorer 11.^{[36][37][38][39]} Internet Explorer initially failed most of the official WebGL conformance tests, but Microsoft later released several updates. The latest 0.94 WebGL engine currently passes ~97% of Khronos tests.^[40] WebGL support can also be manually added to earlier versions of Internet Explorer using third-party plugins such as IEWebGL.^[41]
• Microsoft Edge – For Microsoft Edge Legacy, the initial stable release supports WebGL version 0.95 (context name: "experimental-webgl") with an open source GLSL to HLSL transpiler.^[42] Version 10240+ supports WebGL 1.0 as prefixed. Latest Chromium-based Edge supports WebGL 2.0.

Mobile browsers edit

• Android Browser – WebGL 1.0 is supported on Android as of Chrome 25.^[43] WebGL 2.0 is supported on Android as of Chrome 114.^[44] Chrome is used for the Android system webview as of Android 5.^[44]
• BlackBerry 10 – WebGL 1.0 is available for BlackBerry devices since OS version 10.00^[45]
• BlackBerry PlayBook – WebGL 1.0 is available via WebWorks and browser in PlayBook OS 2.00^[46]
• Internet Explorer – Prefixed WebGL 1.0 is available on Windows Phone 8.x (11+)
• Firefox for mobile – WebGL 1.0 is available for Android and MeeGo devices since Firefox 4.^[47][48]
• Firefox OS^[48]
• Google Chrome – WebGL 1.0 is available for Android devices since Google Chrome 25 and enabled by default since version 30.^[49]
• Maemo – In Nokia N900, WebGL 1.0 is available in the stock microB browser from the PR1.2 firmware update onwards.^[50]
• MeeGo – WebGL 1.0 is unsupported in the stock browser "Web." However, it is available through Firefox.^[48]
• Microsoft Edge – Prefixed WebGL 1.0 is available on Windows 10 Mobile.^[51]
• Opera Mobile – Opera Mobile 12 supports WebGL 1.0 (on Android only).^[52]
• Safari on iOS – WebGL 1.0 is available for mobile Safari in iOS 8.^[53] WebGL 2.0 is available for mobile Safari in iOS 15.^[44]
• Sailfish OS – WebGL 1.0 is supported in the default Sailfish browser.^[54]
• Tizen – WebGL 1.0 is supported^[55]

Utilities edit

The low-level nature of the WebGL API, which provides little on its own to quickly create desirable 3D graphics, motivated the creation of higher-level libraries that abstract common operations (e.g. loading scene graphs and 3D objects in certain formats; applying linear transformations to shaders or view frustums). Some such libraries were ported to JavaScript from other languages. Examples of libraries that provide high-level features include A-Frame (VR), BabylonJS, PlayCanvas, three.js, OSG.JS, Google’s model-viewer and CopperLicht. Web3D also made a project called X3DOM to make X3D and VRML content run on WebGL.

Games edit

There has been an emergence of 2D and 3D game engines for WebGL,^[56] such as Unreal Engine 4 and Unity.^[57] The Stage3D/Flash-based Away3D high-level library also has a port to WebGL via TypeScript.^[25][58] A more light-weight utility library that provides just the vector and matrix math utilities for shaders is sylvester.js.^[59][60] It is sometimes used in conjunction with a WebGL specific extension called glUtils.js.^[59][61]

There are also some 2D libraries built atop WebGL, like Cocos2d-x or Pixi.js, which were implemented this way for performance reasons in a move that parallels what happened with the Starling Framework over Stage3D in the Flash world. The WebGL-based 2D libraries fall back to HTML5 canvas when WebGL is not available.^[62] Removing the rendering bottleneck by giving almost direct access to the GPU has exposed performance limitations in the JavaScript implementations. Some were addressed by asm.js and WebAssembly (similarly, the introduction of Stage3D exposed performance problems within ActionScript, which were addressed by projects like CrossBridge).^[62]

Content creation edit

As with any other graphics API, creating content for WebGL scenes requires using a 3D content creation tool and exporting the scene to a format that is readable by the viewer or helper library. Desktop 3D authoring software such as Blender, Autodesk Maya or SimLab Composer can be used for this purpose. In particular, Blend4Web allows a WebGL scene to be authored entirely in Blender and exported to a browser with a single click, even as a standalone web page.^[63] There are also some WebGL-specific software such as CopperCube and the online WebGL-based editor Clara.io. Online platforms such as Sketchfab and Clara.io allow users to directly upload their 3D models and display them using a hosted WebGL viewer.

Environment-based tools edit

Starting from Firefox Version 27, Mozilla has given Firefox built-in WebGL tools that allow the editing of vertices and fragment shaders.^[64] A number of other debugging and profiling tools have also emerged.^[65]

• List of WebGL frameworks
• Experience Curiosity – WebGL simulation of the Mars rover Curiosity
• glTF – originally known as WebGL Transmissions Format or WebGL TF
• WebXR
• Java OpenGL – OpenGL library for the Java programming language
• WebGPU