A 4096-pixel texture is not automatically high quality, and a 512-pixel texture is not automatically optimized. The useful size depends on how large the surface appears during real gameplay, how close players can get, whether the material repeats, and whether unique details must remain readable. Server owners reviewing editable map assets can make better decisions by testing on-screen coverage instead of enforcing one dimension across every file.
Start from the closest intended view
Identify the nearest normal camera position for each surface category. A wall behind a counter may fill most of the screen; a ceiling duct may never occupy more than a narrow strip. Ignore free-camera inspection unless administrators regularly use that view. Capture screenshots at the production resolution and field of view, then note which textures dominate the frame. Those are the candidates that deserve more resolution or better material construction.
- Hero surfaces: branding, murals or unique counters seen at close range.
- Repeated surfaces: concrete, tile, metal or fabric designed to tile.
- Background surfaces: ceilings, distant façades and blocked areas.
- Small props: objects whose texture occupies limited screen space.
Reduce dimensions one step at a time
Work on a staging copy. For a suspected oversized texture, create a version at the next lower power-of-two dimension, preserve the original format and mip chain, then repeat the same screenshot. Compare edge clarity, material breakup and any required readable detail. If the reduced version is visually equivalent at the closest intended view, keep it and continue only if another step remains acceptable.
The right texture size is the smallest version that survives the closest real gameplay view without visible loss.
Treat width and height separately when the artwork is strongly rectangular. A long narrow sign does not always need a square allocation. Preserve aspect ratio and avoid scaling a rectangular design into a square file merely for convenience. Also check whether empty transparent space consumes most of the image. Cropping unused space and correcting UVs can save more than an indiscriminate quality reduction.
Protect repetition and material consistency
Large floors and walls usually benefit from a tiling base material rather than one enormous unique image. Repetition can be broken with decals, vertex color, props or smaller localized details. When reducing a texture, inspect the full material set together. A sharp normal map paired with a heavily reduced base color can look inconsistent, while oversized auxiliary maps can preserve cost without a visible benefit.
- Keep the original file outside the stream folder for rollback.
- Change one material set per comparison.
- Verify mipmaps are present after export.
- Check day, night and strong interior lighting.
- Walk and drive past the surface to look for shimmer.
Use naming and evidence that survive handoff
Record the texture dictionary, texture name, original dimensions, tested dimensions and accepted result. Include one close screenshot and one normal gameplay screenshot. Do not report only total folder size; compression and packaging can hide which individual textures are unreasonable. The purpose of the review is to identify specific files that can change safely, not to chase an arbitrary percentage.
Review duplicate materials before resizing files. Two textures with different names may contain the same concrete, metal or fabric image, especially after assets are combined from several editable sources. Hashes can identify exact duplicates, while a visual review catches near-duplicates with minor color changes. Consolidation may be appropriate, but only when UVs, material parameters and licensing allow it. Keep branding and unique artwork separate. Document every redirect or renamed texture so future editors do not restore the duplicate by accident. This cleanup is different from blind compression: it removes redundant content while preserving the dimensions proven necessary by the gameplay screenshots.
This method is especially useful when adapting a branded or editable MLO. KAIZO’s Map & MLO Editing service can adjust textures, lighting, props and branding where the license permits modification, but the strongest brief identifies exact material names and viewing conditions. Approving texture sizes from on-screen evidence protects visual quality while removing resolution that players never receive as meaningful detail. Repeat the same screenshot set after every major map revision to prevent quiet regressions.
