Size limits for mobile
The guidelines that keep a 3D jewellery model fast and stable on a phone.
A phone has less graphics power and less memory than a desktop computer. A heavy model loads slowly on a phone. On an iPhone, a model that uses too much memory makes the page reload.
The values in this table are guidelines. The correct value depends on the product.
| Item | Guideline | Reason |
|---|---|---|
| Polygon count | Less than about 200,000 for each model | A heavier model loads slowly on a phone. |
| Memory on an iPhone | About 350 MB to 400 MB, different for each iPhone model | iOS Safari reloads the page above this limit. |
| Texture maps | 1024 x 1024 pixels or smaller | Smaller textures use less memory. |
| Diamonds | Few gem layers, and shared cache keys in Playground | Each cache key uses memory. The editor shows a warning at five or more cache keys. |
| File size | The limit for one file depends on your plan | Refer to File limits. |
How to make a model lighter
- In Rhino, use the
ReduceMeshcommand on heavy parts. - Use block instances for identical parts, such as small stones, prongs and chain links.
- Use a mesh resolution that shows the shape correctly, and no more.
- Keep Compression on when you upload the file.
- In Playground, set a lower renderer scale for mobile.
Do a test on a real phone
Do a test on a mid-range phone, not only on your own phone. A new phone can hide a problem.