There's really no need for that. WebGL and WebGPU have no concept of file types. Whether it's Wavefront OBJ or COLLADA or glTF or some jankasaurus of JSON loade

There's really no need for that. WebGL and WebGPU have no concept of file types. Whether it's Wavefront OBJ or COLLADA or glTF or some jankasaurus of JSON loaded out of a database, WebGL isn't going to and shouldn't have to understand it natively. It's on the app developer to translate that to vertices, texture maps, etc. And that's going to change a lot depending on what sort of abstraction layer you're using on top of WebGL, e.g. Three.js or Babylon.js or whatever. If anything, having native support for specific 3D interchange formats would constrict and over complicate the available options to app and 3D framework developers.