You can create subfolders as well as custom filenames for storing your rendered images using the section in the Render Settings: Common tab.
This section describes the tokens that you can input to create the subfolders and filenames. Should you decide not to input
any of the tokens described below, Maya creates default subfolders in which it saves the rendered images.
For more information regarding project file locations, see File > Set Project.
Default behavior of rendered images and directories
By default, Maya saves rendered images to the following subfolders:
Scenes with more than one render layer and renderable camera
If your scene consists of more than one render layer, then a subfolder is created for each layer.
Similarly, if your scene consists of more than one renderable camera, a subfolder will be created for each camera.
For example, a scene with two render layers and two renderable cameras would save out rendered images to subdirectories as
Scenes with only one render layer or only one renderable camera
By default, a layer subfolder is not created for a scene with only one render layer. Therefore, a scene with two renderable
cameras but only one render layer creates subfolders as follows:
Similarly, a camera subfolder is not created by default for a scene with only one renderable camera. Therefore, a scene with
two render layers but only one renderable camera creates subfolders as follows:
If a scene has only one render layer (or no layers at all) and only one renderable camera, then subfolders are not created by default and Maya saves the scene as MyScene.iff.
Creating subfolders and filenames for rendered images
The following rendered image filename options and tokens can be combined to create subfolders and custom image names for rendered
images. Enter these options in the field of the Render Settings: Common tab.
Use the tokens in conjunction with different separators between them. To create subfolders, use the slash (/) separator as in <RenderLayer>/<Camera>/<Scene>. Use any other separator, for example, underscore (_) and dash (-), to separate the tokens in your image file name.
You can repeat options within the specification, and you can also specify any text you like in the image file name or path
(for example, .TEST or _final to indicate the kind of render that you are performing).
Rendered image filename options (tokens)
Adds the layer name to the created subfolder or image file name (for example, layer1).
When using render passes with the Maya software renderer, if more than one pass is created for the layer, then pass names
are appended to the layer name. The format used is layer_pass (for example, layer1_beauty). For more information on passes,
see Work with render passes. When using multi-render passes with the mental ray renderer, a directory is created for each pass. See Multi-render passes for more information.
Adds the scene name to your subfolder or image file name.
Adds the renderable camera name to the created subfolder or image file name (for example, camera1).
If your scene is set to render fields, then field names are appended to the name; for example, camera_odd or camera_even.
Adds the render pass file group name to the created subfolder or image file name (for example, IndirectIllum). See Pass Group Name for more information regarding the pass group name.
Add the render pass node name to the created subfolder or image file name(for example, diffuseNoShadow).
Many different types of render passes are available for selection using the Render pass Attribute Editor, for example, beauty, shadow, specular, refraction, and so forth. When you use this render token, a unique abbreviation of
the pass type, of less than 6 characters, is appended to your output file name, for example, REFR for refraction pass.
Adds the extension to the created subfolder or image file name.
Adds the version label that you have selected to the created subfolder or image file name. This option can be a numeric version
number, the current date, the current time, or any custom version label. Customize this token using the attribute.
Setting up your file name prefix using the command line
In addition to setting up your file name prefix using the render tokens in the window: tab, you can also use the command line to set up the file name prefix using the -im flag.You must include the angular brackets for each render token and wrap the string with quotation marks.Some of the shorthand
notations, for example, %l for layer and %c for camera, are still supported for backwards compatibility. However, not all
tokens have a shorthand equivalent.Create subdirectories by adding a / (slash). Any alpha numeric text, in addition to underscore
(_) and dash (-), can be used to separate the tokens in your image file name.
Render –r scenefilename -im "<Camera>/<RenderLayer>/Draft_3_<Scene>_<RenderPass>"
OpenEXR file format
Among the available multi-channel file formats, OpenEXR is the only file format where multi-channel is being leveraged. Therefore,
multiple render passes can be concatenated into a single-multi-channel .exr file. Use the and attributes in the Render Settings: Common tab to customize the naming of your OpenEXR channels.
In order to use these attributes, your scene must contain at least one render pass. Also, you must select OpenEXR as your
file format for these attributes to become active.
Select the mode under the attribute to use the <RenderPassType>:<RenderPass>.<Camera> tokens to name your channels. This is the default option.
Select the mode under the attribute to customize your OpenEXR channel names. Choose from the render tokens listed in Rendered image filename options
EXR version 1.7 supports 252 character channel names. The limit is 252 characters to save room for an extension of up to 3
characters used to differentiate individual channels (for example .R for the red channel). However, EXR version 1.7 is currently supported by few external applications, and embedding channel
names longer than 31 characters may break compatibility with external applications that do not support it. By default, channel
names are truncated to 31 characters for backward compatibility. You can create and set MAYA_EXR_LONGNAME to 1 to allow long
channel names of 252 characters so that they are not truncated. See Image format for more information on the OpenEXR format. See Rendering environment variables for more information about the MAYA_EXR_LONGNAME environment variable.
Do not use the token in your field if you are using the multi-channel OpenEXR format. Using the token creates a file for each render pass instead of writing to a multi-channel .exr file.
See Render Settings: Common tab for more information.
In addition to the rendered image filename tokens discussed above, you can also use the drop-down list to customize your image name by adding the frame number to your image name. For example, if you choose name#.ext with a Frame padding of 4, and the scene name is MyScene, then the rendered image would be named MyScene0001.iff.
- If you choose not to enter any tokens in the attribute, the following subfolders are created by default:
- If you choose to use the field in conjunction with the File name prefix attribute, you can add the frame number to your image name also. Assume that you choose the name_#.ext option with a of 2. The following entry produces a layer name subfolder and adds 1) the camera name, 2) the scene name, and 3) the frame
number to the name of the rendered image. The -(dash) separator is added to separate the camera and scene names.
For example, layer1/camera1-MyScene_01.iff
- The following entry produces no subdirectories, but simply a flat file structure. The _(underscore) separator separates the
scene, layer and camera names.
For example, MyScene_layer1_camera2_01.iff
- The following entry produces a scene name subdirectory, then the layer subdirectory, then a camera subdirectory, and then
adds the scene name to the name of the rendered image, and adds ‘TEMP’ to the image name:
for example, MyScene/layer1/camera1/MySceneTEMP_01.iff
Except where otherwise noted, this work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License