--- title: "Images" canonical: "https://documentation.chaos.com/space/DOCSGUIDE/113289651/Images" format: markdown --- > ❌ DO NOT use images that are not attached to the page itself! ## **UI Screenshots** --- ### **Capturing** Make sure to test your monitor to determine whether ClearType should be enabled or disabled. If you’re unsure, take two screenshots – one with ClearType on and one with it off – and compare them visually. If you still can’t decide, ask another member of the Docs team for their opinion. Make sure you use dots and not commas for floating numbers in the user interface. On Windows, this setting can be adjusted by going to **Control Panel > Region > Formats > Additional settings**. ![image](media://35b3c56f-a3a1-4faf-9524-d364d985c39d) ### **Saving** Save as JPG/JPEG. This format saves memory on the page and is preferable to use. Make sure it is in its best quality. UI screenshots appear with artifacts if the JPG is compressed, thus use at least 85% (100% is fine for UI screenshots). When saving UI screenshot examples, use the following naming convention to make it easier to know the main topic of that image weeks or months from when it was originally created or posted. *[app]####_(VRay)##_[topic/page]_[description].jpg* Example: *max2016_33_areaLight_defaultUI.jpg* > ℹ️ In some individual cases where transparency is required, you may use PNGs if necessary. Use the **Add alt text** option to add a name for the image, which will be displayed when you hover over the image in Refined. ![TechGuide_AltText.png](media://b9d8a876-f7e2-4a8f-970d-5f3be6459e4a) Example: *max2016_33_areaLight_mainTab.jpg *could become *AreaLight_Main_Tab *or just *MainTab.* ### **Layout** > ⚠️ Always display screenshots in their **Original** size. Confluence uses a white background. If your screenshot/image/render is white-ish or light color, use a Border to outline it. ## **Renderings** --- ### **Saving** If you can, save the render as a JPG (should it not reduce the quality). You can also use the PNG format, but the presumption is to save memory on the page and to load it faster. When saving render examples, use the following naming convention to make it easier to know the main topic of that image weeks or months from when it was originally created or posted. [app]####_(VRay)##_[topic/page]_[description].png Example: *maya2016_31501_aerialPerspective_distance500m.png* ### Resolution Currently, the docs pages are designed with a browser width ranging from 1024-1280 pixels across. Therefore, most screenshots or renders are sized with this in mind. Larger images take longer to load and the return is not worth it. ### Multiple Images If multiple rendered images are to be placed side by side, it is acceptable to upload a 1024 version of each image. Multiple renderings in a set should have the same resolution and aspect ratio, so when they are sized to **Original Size **they all have the same-sized display. ### Screenshots and Renderings Together When showing the use of a UI element in a rendering, take a screen capture of the same view in the UI (such as the object in a wireframe or shaded viewport) and place it side-by-side with the rendering. The images do not have to have the same resolution, but they must have the same aspect ratio to look good when placed side by side. > ℹ️ Add an Alt text to each image you upload - be it render, screenshot, gif or else. An Alt text is found in Properties when you select the image. It enhances the SEO. ## **Laying out Multiple Images ** --- ### More Than Three Images Use the two- and three-image layouts as needed to complete the set. Start at the top of this table and use the first layout that fits the description. | **Is the total number of images:** | **Then use:** | | --- | --- | | Divisible by 3? | Three-image layout all the way down | | Divisible by 2? | Two-image layout all the way down | | Everything else | Use three-image until the last rows. Use 3-2 or 2-2 on last two rows to complete the set. Last row is always a 2. | For example, for a 6-image layout you would use two three-image layouts, not three two-image layouts. Examples of layouts for more than three images. Note that in numbers not divisible by 3 or 2, the last row is always a 2. | **Number of images** | **Image layout sequence** | **Because it's:** | | --- | --- | --- | | 4 | 2-2 | Divisible by 2 | | 5 | 3-2 | Not divisible by 3 or 2 | | 6 | 3-3 | Divisible by 3 | | 7 | 3-2-2 | Not divisible by 3 or 2 | | 8 | 2-2-2-2 | Divisible by 2 | | 9 | 3-3-3 | Divisible by 3 | | 10 | 2-2-2-2-2 | Divisible by 2 | | 11 | 3-3-3-2 | Not divisible by 3 or 2 | | 12 | 3-3-3-3 | Divisible by 3 | ### Examples
Examples 6-Image Arrangement ![TechGuide_Example1.png](media://03fbf36f-37af-4df7-93fd-a1e3378d4fb8) --- 5-Image Arrangement ![TechGuide_Example2.png](media://65e91118-97cc-4207-9964-77d2d41a8279) --- 4-Image Arrangement ![TechGuide_Example3.png](media://9edaf455-3b93-41bb-9b6c-c124f3d1d2dc)