CheckMate Pro Specification

This article contains the full specification for CheckMate Pro, TurboSquid’s highest quality standard for 3D models. To see the condensed CheckMate Pro Checklist, you can go HERE.
v. 2.1
July 15th, 2019

  1.    Limitations on CheckMate Pro Certification

1.1   Quality – The 3D model must have a high level of aesthetic appeal as well as workability. If the model is intended to represent a real-world object, it must accurately represent that object. Quads and triangles must be intelligently distributed for good edge flow and clean topology.

1.2   Pricing

1.2.1   Product pricing must conform to the CheckMate pricing matrix.

1.2.2   Product pricing must be equal to or above the average selling price of comparable models. TurboSquid reserves the right to make changes to prices as necessary.

1.3   File Formats

1.3.1   Native file format must pass inspection before other file formats are inspected.

1.3.2   The following file formats are eligible for inspection:

  • 3ds Max (.max) (Renderers Supported: Scanline / V-Ray / Corona / Arnold / IRay / Mental Ray / Redshift)
  • Maya (.ma / .mb) (Renderers Supported: Software / Hardware / Mental Ray / V-Ray / Arnold / Redshift)
  • CINEMA 4D (.c4d) (Renderers Supported: Advanced / Physical / Arnold / V-Ray / Redshift)
  • Lightwave (.lws) (Renderers Supported: Default)
  • Blender (.blend) (Renderers Supported: Standard / Cycles/ Eevee)   Product must include at least one of the above file formats as its native file format in order to be considered for CheckMate Pro certification.   Other file formats are not inspected for CheckMate Pro certification.

1.3.3   CheckMate Pro certification is awarded on a per-format basis. The native file format must pass CheckMate Pro certification in order to get the Pro badge, but if another certifiable non-native file format fails inspection, the native format (and product) will still be marked as CheckMate Pro certified. The non-native file must, as a minimum, pass the requirements for CheckMate Lite inspection in that it must open and render without errors.

1.4   Scenes, Sets & Collections

1.4.1   Scenes and sets are eligible for certification.

1.4.2   Collections are not eligible for certification unless all of the models within that collection have already been certified individually as CheckMate Pro or CheckMate Lite.

  • Collections that contain all CheckMate Pro models can be submitted for Pro certification.
  • Collections that contain all CheckMate Lite models can be submitted for Lite certification.
  • Collections that contain both CheckMate Lite and Pro models can be submitted for Lite certification.

1.5   Standard or Editorial License Only – Models with Custom Licenses are not eligible for certification.

1.6   SquidGuild Only – CheckMate Pro Certification is available only for 3D models published by SquidGuild members.

1.7   Payment Information – In order to have 3D models CheckMate Certified, the publishing member must fill out accurate and up-to-date Payment Information for the TurboSquid account.

  1.    Standards for 3D Model Inspection

2.1  Geometry

2.1.1   No isolated vertices

2.1.2   No coincident vertices

2.1.3   No coincident/coplanar faces

2.1.4   Face normals point outward – by outward we mean the appropriate direction for correct rendering, with no normals incorrectly flipped.

2.1.5   No empty objects – All objects should have geometry or splines or be null/control helpers. No empty objects that have names but nothing else permitted.

2.1.6   Geometry must not have open edges or borders that cause see-through cracks in the model when rendered. Note: Only models inspected after June 15, 2013 are guaranteed to meet this point of the specification.

2.2  Topology

2.2.1   Quads and Triangles only

2.2.2   Mostly quads – The model must use quads as much as possible. A range of up to 20% triangles is acceptable for most models, but you should actively endeavor to minimize their usage in your work. Models are inspected manually to ensure excessive triangles aren’t present.

Note that realtime models will often have a much higher percentage of triangles to meet the requirement of minimum geometry possible to form the object.

2.2.3   Clean edge flow – Model must have the best possible edge flow, with sufficient geometry to meet these requirements without superfluous geometry. Note: Only models inspected after June 15, 2013 are guaranteed to meet this point of the specification.   Subdividable Topology – Model can be cleanly subdividable for higher detail and still retain shape of model.   Poles with more than 5 edges on the model are highly discouraged as it can indicate sloppy topology to a customer. If poles are included in your model, you must add the following note to your Product Description.

NOTE:  This model contains poles (more than 5 edges that converge to a single vertex.)”   Holding/support edges present to retain shape after subdivision   Exceptions:   Exception for very small, insignificant objects within the model/scene: Such objects do not have to meet the criteria above. Objects such as screws, bolts, rivets, wires, and other objects which are very small in comparison to the overall model size, do not have to follow the Clean Edge Flow rules.   Exception for one-sided objects with opacity map: Objects that represent a thin real-life object as a one-sided object, where the shape of the object is depicted via an opacity map, do not have to follow the Clean Edge Flow rules.

Examples of this exception are leaves, petals, decals, paper, cloth. This exception does not apply to fully three-dimensional objects such as thin boxes.   Exception for realtime models – Models intended for game engines, realtime display, or background elements must have the lowest number of polygons possible while still retaining the model’s shape, but do not have to conform to the subdivision points above. For such models, a high percentage of triangles is allowable, provided they are necessary to make the model shape with the lowest number of polygons possible.

2.2.4   Crease value – Value of the Crease or Open SubDiv function within your 3D application must be 0 for all edges. Note: Only models inspected after June 15, 2013 are guaranteed to meet this point of the specification.

This requirement ensures that a subdividable model, when converted to other formats, will retain the same shape when subdivided. If the model is a realtime model (not subdividable), there is no reason to have a Crease value other than 0.

2.3  Real-World Scale

2.3.1   Real-world scale within 1-3% – Model can use any units to achieve real-world scale. If the model does not have an exact real-world counterpart (such as a human character or an unbranded car), the model must use the size/scale of comparable objects in real life.

2.3.2   Exception for exceedingly large/small models – Models of objects that have a real-world scale at a microscopic or astronomical level, such as amoebas and solar systems, are excepted from having real-world scale.

2.4  Position and Orientation

2.4.1   Base of model must be positioned at the Origin (0,0,0).

2.4.2   The entire model should sit on or just above ground plane.

2.4.3  The model should be oriented to World up-axis – The obvious “up” side of the model must be pointing toward the World up axis. In other words, the model can’t be lying on its side or upside-down when the file is opened. For objects that can be oriented in multiple ways (e.g. books, pencils, etc.), the artist is free to choose the up-axis, but this must be reflected in the presentation images so a customer’s expectations are matched by what is shown.

2.4.4  The native model file must be in the same position and framing as the Search image. Additional non-native file formats that are published simply need to open so the full model is visible in the viewport with no hidden parts but do not have to match pose and framing of the native file.  Native models are exempt from meeting the same position and framing as the Search image as long as the work needed to match the imagery is trivial (minor repositioning or rotation of model).  The full model will still need to be visible in the viewport with no hidden parts.

2.5   Transforms

2.5.1   The position and rotation transforms must be frozen/reset.

2.5.2   All objects at 100% scale at object level.

2.6   Naming and Organization

2.6.1   Descriptive and unique object namesDefault object names are not acceptable. They should be changed to be descriptive of the object and easy-to-understand when reviewed by a customer.

2.6.2   Model file includes only the 3D model being sold – No extraneous helpers, shapes, splines, or other unexpected objects not specifically needed for model functionality.

2.6.3   Model includes a grouping or hierarchy for moving all objects in model together.

2.6.4   All geometry is contained in a single layer structure, with the layer having the same name as the product. Note: Only models inspected after June 15, 2013 are guaranteed to meet this point of the specification.

  • 3ds Max – Layers
  • Maya – Display Layers
  • CINEMA 4D – Layers
  • Lightwave – Include the .LWS with the model and organize using a null object
  • Blender – All elements of the model on a single layer

2.7   Textures and Materials

2.7.1   At least one material must be applied to each object to represent real-world object surfaces. The customer should be able to render the model upon purchase and get quality surface representation.

2.7.2   Textures applied where appropriate

2.7.3   Materials and Bitmap texture files named descriptively. Bitmap filenames Image, Pic or Picture plus a number are not acceptable. Likewise, material filenames 01-Default, Blinn01, Mat are not acceptable.

2.7.4   No texture paths referenced by the model. All texture paths must be stripped from the model.

2.8   UVs 

A model with mapped textures must meet these requirements:

2.8.1   No obvious texture stretching on model.

2.8.2   UV Seams are hidden in less visible areas of model.

2.8.3   People and animals must have unwrapped UVs – This standard does not apply to larger scenes where the character or animal is not the focal point.

2.9   Rigging 

2.9.1   Transforms must be frozen/reset unless model is animated.

2.9.2   Hierarchy objects must be uniquely and appropriately named.

2.9.3   Rig must function as expected – Rig must perform simple deformations.

2.9.4   Custom rig must include instructions – A Readme, PDF document, or other documentation on how to use the rig. Rigs that use Biped or CAT are not required to have a readme unless there are custom controls.

2.9.5 Non-Rigged Character Models should never include Product Shot images of poses that are not included with the model.

2.9.6 For other Non-Rigged Models (e.g. vehicles/appliances), showing poses for non-character, unrigged models is acceptable with the following two requirements: An additional line included with product description “Only default Pose included. Other poses shown are possible by rotating elements as pivots are placed properly.” The model’s pivot points are placed to allow the pose by the customer without further modification.

2.10   Animation 

2.10.1   Animation must play smoothly – No obvious glitches or hitches.

2.10.2   Animation designated as looping must loop smoothly.

2.10.3   No spikes in your animation graph that cause a sudden and unnatural movement or rotation during playback..

  1.    Standards for Product Presentation

3.1   Product Preview Images

3.1.1   All CheckMate imagery must meet the presentation standards that are outlined within the Product Imagery Checklist.

3.1.2   Unwrapped UV Image Requirements: At least one (1) image of the unwrapped UVs of your model if one of the following options is selected for the model’s Unwrapped UVs attribute within the publisher interface:

  • Yes, overlapping
  • Yes, non-overlapping
  • Mixed   Minimum resolution of 800 x 800.  Square (1 to 1) aspect ratio pixel resolution is recommended but not required.   Image shows the entire Diffuse texture image overlaid by the 0-1 UV space.

If no texture is applied to the object, background color on thumbnail should match the material color applied to the object. The image should show the main texture, pattern, or color on the object, not secondary textures such as bump or specular maps.

3.2   Main Product Files

3.2.1   Includes at least one certifiable file format (See 1.3 File Formats).

3.2.2   Native file format specified within the publisher. The Native file represents the 3D application you originally built the model in.

3.2.3   Software version and renderer version are specified for all certifiable files.

3.2.4   All required files archived with product file in one of the following three ways:

  • All bitmap textures are archived with each certifiable model file in a flat file structure.
  • All bitmap textures are archived with each certifiable model file in a single subfolder beneath the main product file.
  • All bitmap textures required are placed into a single, named ZIP file and uploaded once as a Textures Supporting Items product in the TurboSquid publisher.  Certifiable model files are each placed into their own named ZIP files and uploaded on their own. See Bitmap Texture Pathing.

3.2.5   Archives should not contain multiple renderer versions; separate download archives should be provided for different renderers, even from the same 3d application.

3.3   Product Name Requirements

3.3.1   Product Name must be in English.

3.3.2   Product Name must be composed of adjectives and nouns pertaining to the model, separated by spaces.

3.3.3   Product name must not contain file extensions

3.3.4   All words in the Product Name except articles, conjunctions and prepositions must have initial capital letter. Words that represent acronyms can be all caps, but product Name should not be all caps.

3.4   3D Model Specifications

3.4.1   Polygon Count value matches poly count in native file format. If you’ve applied subdivision to the native file format which is removable (as with a TurboSmooth modifier in 3ds Max or an editable history in Maya) you must enter the polygon count without subdivision.

3.4.2   Vertex Count value matches vertex count in native file format before subdivision.

3.4.3   In the Geometry field within the publisher, one of these two choices is selected:

  • Polygonal Quads/Tris
  • Polygonal Quads only

3.4.4   All product specification fields are accurate with respect to model being submitted for certification.

3.5   Description Requirements

3.5.1   All bitmap texture resolutions specified.

3.5.2   Renderer used for preview images specified (if not default for native software).

3.5.3   Third-party plug-ins or renderers used or referenced in model explicitly specified in your description. If the renderer in the model file is set to a non-default renderer, or if materials are those from a non-default renderer, state this in Description.

3.5.4   Rigging type specified (if any) – If model is rigged, state what system is used for the rig (Biped, CAT, etc.) or if it is custom using your software’s bones and linking tools.

3.5.5   Animation details specified – Frame length, frames per second used, content of animation, etc.

3.5.6   All descriptions should use proper grammar, punctuation, spelling, capitalization, and correct product names.

3.5.7   Real-world scale units must be specified. This does not mean for you to put the length, width and height of your model, simply the units of measurement that were utilized.

3.6   Category

3.6.1   Must be relevant to the model you publish.

3.6.2   Only one category is required.

3.6.3   If two categories are selected, the first category should be the most relevant of the two.

3.7   Keywords

3.7.1   Must be spelled correctly.

3.7.2   Must be relevant to the model published.

3.7.3   Must include at least five (5) unique keywords.

3.8   No Personal Contact Information: This is a requirement for all products published for sale at TurboSquid.

The CheckMate Specifications, CheckMate names, including “CheckMate Pro” and “CheckMate Lite,” and all related branding and logos, whether registered or not, are the property of TurboSquid. TurboSquid retains all ownership of these trademarks and copyrighted material. They are protected by intellectual property laws of the U.S. or in some instances, foreign laws and international treaties. Unauthorized use may violate copyright, trademark and other laws.

CheckMate Specifications may be reused and republished by third parties with permission, with the exception of third parties that sell or distribute 3D content as part of a stock 3D business. In no case may models distributed or sold anywhere other than at (or its affiliates including the SquidGuild Network) be referred to as “CheckMate,” “CheckMate Certified,” “CheckMate Pro,” “CheckMate Lite” or any by similar name referencing CheckMate.

Participants in the CheckMate program who have received certification and would like to use CheckMate branding to promote their own models may do so on other sites, so long as such models are not sold on those other sites.

For any questions or to request permission to republish CheckMate Specifications, please contact