50 MB glTF sample
A glTF file of exactly 52,428,800 bytes. It is a valid GL Transmission Format file, generated by this site. Compare its checksum and test it with the parser used by your application. Use it wherever you need a 50 MB sample, test or dummy glTF file.
Download
sample-gltf-50mb.gltf
50 MB52,428,800 bytes
Download 50 MB glTFCreated in your browser and, in browsers that can stream to disk, sent straight to your downloads list; this can take a minute. No sign-up.
- Type
- model/gltf+json
- SHA-256
470c3944e627a5184c6a672e33099990104dfe89187cf29bc4f1b362d7b16572- Delivery
- Created in your browser from static generator assets (how it works).
What is in this file
A glTF 2.0 scene with one mesh: a height-field terrain of 524,176 vertices and 1,045,458 triangles, stored in a base64 buffer inside the JSON. A padding string in the top-level "extras" member brings the file to the exact size.
| Vertices | 524,176 |
|---|---|
| Triangles | 1,045,458 |
| glTF version | 2.0 |
| Buffers | 1 (embedded, base64) |
| Materials | None (default) |
How the file begins
The opening lines of sample-gltf-50mb.gltf, exactly as they appear in the file.
00000000 7b 22 61 73 73 65 74 22 3a 7b 22 76 65 72 73 69 |{"asset":{"versi|
00000010 6f 6e 22 3a 22 32 2e 30 22 2c 22 67 65 6e 65 72 |on":"2.0","gener|
00000020 61 74 6f 72 22 3a 22 53 61 6d 70 6c 65 54 65 73 |ator":"SampleTes|
00000030 74 46 69 6c 65 73 20 73 61 6d 70 6c 65 20 66 69 |tFiles sample fi|Preview
Creates the file in your browser and shows the first 64 KB of it.
Where 50 MB matters
A 52,428,800-byte file: exactly the size at which Git hosting on GitHub starts warning about large files, and about the limit for a zipped AWS Lambda package uploaded directly.
Use this file for
- Finding the first upload limit in a new stack
- Testing 3D upload and web preview
- Checking loaders with embedded and external buffers
Testing notes for glTF
- A file can declare extensions it requires, such as Draco mesh compression. A loader without that extension has to refuse the file.
- A .gltf file often refers to separate .bin and texture files. Uploading the JSON alone gives a model with no geometry. The samples here embed their data, so one file is enough.
Technical details
| File name | sample-gltf-50mb.gltf |
|---|---|
| Format | glTF (GL Transmission Format) |
| Extension | .gltf |
| MIME type | model/gltf+json |
| Size | 52,428,800 bytes (50 MB) |
| Kind | Text |
| SHA-256 | 470c3944e627a5184c6a672e33099990104dfe89187cf29bc4f1b362d7b16572 |
| Created | 2026-10-23 |
| Validation | See the listed size and SHA-256. Small downloads are checked in the browser; verify streamed downloads manually. A hash match does not prove parser compatibility. |
| Preview | Available on this page |
| Source | Generated in your browser by this site's generator; not copied from elsewhere |
| Licence | Free to use, modify and redistribute (terms) |
| Category | 3D Models |
Check the stated structure and checksum against your application requirements. As with any download, scan the file with your own security tools before opening it. How files are made and checked
Verify your copy
This file is created in your browser, so it has no direct URL for curl or wget. The generator is designed to produce reproducible bytes. After saving, compare the checksum with the SHA-256 value above.
sha256sum sample-gltf-50mb.gltf # Linux
shasum -a 256 sample-gltf-50mb.gltf # macOSOn Windows, run Get-FileHash sample-gltf-50mb.gltf -Algorithm SHA256 in PowerShell. For scripts and pipelines, save the file once and keep your own copy.
Related files
Questions about this file
- Is this file exactly 50 MB?
- Yes. It is 52,428,800 bytes, which is 50 MB in the binary units that operating systems and server limits use (1 KB = 1,024 bytes).
- What is inside the 50 MB glTF file?
- A glTF 2.0 scene with one mesh: a height-field terrain of 524,176 vertices and 1,045,458 triangles, stored in a base64 buffer inside the JSON. A padding string in the top-level "extras" member brings the file to the exact size.
- Do the glTF samples need a separate .bin file?
- No. The vertex and index data are embedded in the JSON as a base64 data URI, so each sample is a single self-contained file.