[{"data":1,"prerenderedAt":1067},["ShallowReactive",2],{"\u002Fguides\u002Fdifferent-image-per-instance":3,"\u002Fguides\u002Fdifferent-image-per-instance-addon":758},{"id":4,"title":5,"addon":6,"body":7,"description":746,"extension":747,"meta":748,"navigation":749,"path":750,"poster":751,"rawbody":752,"seo":753,"stem":754,"updated":755,"video":756,"__hash__":757},"guides\u002Fguides\u002Fdifferent-image-per-instance.md","Different image on each instance in Blender","image-per-instance",{"type":8,"value":9,"toc":730},"minimark",[10,14,19,35,38,42,45,78,81,85,88,93,96,111,115,141,270,276,280,297,301,304,353,356,385,388,392,395,463,473,479,483,493,510,513,517,524,527,531,569,573,662,666,676,679,718,726],[11,12,13],"p",{},"Blender has no \"image index per object\" input, so one shared material shows one image everywhere. To give each object or instance its own picture, either use one material per image, or pack all images into one atlas and let each object pick its cell through a number the shader can read (an object custom property, or a named attribute stored on a Geometry Nodes instance). The first is fine for a handful of images. The second is the one that scales to dozens, and I ran every step below in Blender 4.2, 4.5 and 5.2.",[15,16,18],"h2",{"id":17},"why-the-obvious-node-setup-only-gives-colours","Why the obvious node setup only gives colours",[11,20,21,22,26,27,30,31,34],{},"The first thing most people try is ",[23,24,25],"strong",{},"Object Info",". Its ",[23,28,29],{},"Random"," output is a different number from 0 to 1 for every object, and for every Geometry Nodes instance too. Plug it into a ",[23,32,33],{},"Color Ramp"," and each object gets its own colour.",[11,36,37],{},"That is a colour, not a picture. The Image Texture node loads one image and has no socket for \"which image\". Random into a Color Ramp suits randomised tints and stops there. What you need is a number per object that chooses an image.",[15,39,41],{"id":40},"method-1-one-material-per-image","Method 1: one material per image",[11,43,44],{},"For a handful of pictures this is the simplest thing that works and needs no node maths.",[46,47,48,56,71],"ol",{},[49,50,51,52,55],"li",{},"Select the object and open the ",[23,53,54],{},"Material Properties"," tab.",[49,57,58,59,62,63,66,67,70],{},"Create a material, add an ",[23,60,61],{},"Image Texture"," node, open the picture and connect ",[23,64,65],{},"Color"," to the ",[23,68,69],{},"Base Color"," of the Principled BSDF.",[49,72,73,74,77],{},"Duplicate the object (",[23,75,76],{},"Shift D",") and give the copy the next material, one object per picture.",[11,79,80],{},"It breaks down when pictures multiply: every new one means a new material and a manual assignment. Instances from Instance on Points or the Array modifier share the material of their source, so they cannot get different pictures this way at all.",[15,82,84],{"id":83},"method-2-an-atlas-with-a-uv-offset-per-object","Method 2: an atlas with a UV offset per object",[11,86,87],{},"This is the method that scales. All pictures go into one image laid out in a grid, and the shader shifts the UVs so each object looks at one cell.",[89,90,92],"h3",{"id":91},"make-the-atlas","Make the atlas",[11,94,95],{},"Put your pictures into a grid of equal cells in any image editor, for example 2 columns by 2 rows for four images, and save one image. Cell 0 is bottom-left, cell 1 is to its right, and rows count upward, because UV space starts at the bottom-left.",[11,97,98,99,102,103,106,107,110],{},"Set the Image Texture node's ",[23,100,101],{},"Interpolation"," to ",[23,104,105],{},"Closest"," while you test. With ",[23,108,109],{},"Linear",", neighbouring cells can bleed into each other at the edges, so leave a few pixels of padding between pictures when you switch it back.",[89,112,114],{"id":113},"build-the-shader","Build the shader",[11,116,117,118,122,123,126,127,130,131,133,134,136,137,140],{},"Use an index number ",[119,120,121],"code",{},"i"," from 0 to the number of cells minus one. For a grid with ",[119,124,125],{},"cols"," columns and ",[119,128,129],{},"rows"," rows, the cell column is ",[119,132,121],{}," modulo ",[119,135,125],{}," and the row is ",[119,138,139],{},"floor(i \u002F cols)",".",[46,142,143,164,189,203,220,245,254],{},[49,144,145,146,149,150,153,154,157,158,102,161,140],{},"Add ",[23,147,148],{},"Texture Coordinate"," and take its ",[23,151,152],{},"UV"," output into a ",[23,155,156],{},"Mapping"," node. Set ",[23,159,160],{},"Type",[23,162,163],{},"Point",[49,165,166,167,102,170,173,174,173,177,180,181,173,184,173,186,188],{},"Set Mapping ",[23,168,169],{},"Scale",[119,171,172],{},"1\u002Fcols",", ",[119,175,176],{},"1\u002Frows",[119,178,179],{},"1",". For the 2 by 2 atlas that is ",[119,182,183],{},"0.5",[119,185,183],{},[119,187,179],{},". This shrinks the UV square to one cell.",[49,190,191,192,195,196,199,200,202],{},"Add a ",[23,193,194],{},"Math"," node set to ",[23,197,198],{},"Floored Modulo"," with the second value ",[119,201,125],{},". This is the column.",[49,204,191,205,195,207,210,211,213,214,195,216,219],{},[23,206,194],{},[23,208,209],{},"Divide"," by ",[119,212,125],{},", then a ",[23,215,194],{},[23,217,218],{},"Floor",". This is the row.",[49,221,222,223,225,226,228,229,232,233,236,237,240,241,244],{},"Divide the column by ",[119,224,125],{}," and the row by ",[119,227,129],{}," with two more ",[23,230,231],{},"Math > Divide"," nodes, and put the results into ",[23,234,235],{},"X"," and ",[23,238,239],{},"Y"," of a ",[23,242,243],{},"Combine XYZ"," node.",[49,246,247,248,66,250,253],{},"Connect ",[23,249,243],{},[23,251,252],{},"Location"," input of the Mapping node.",[49,255,256,257,260,261,263,264,266,267,269],{},"Connect Mapping ",[23,258,259],{},"Vector"," to the Image Texture ",[23,262,259],{},", and its ",[23,265,65],{}," to the Principled BSDF ",[23,268,69],{}," (or to an Emission node for a screen).",[11,271,272,273,275],{},"Now the only missing piece is how the index ",[119,274,121],{}," gets to each object.",[89,277,279],{"id":278},"option-a-random-index-from-object-info","Option A: random index from Object Info",[11,281,247,282,285,286,289,290,293,294,296],{},[23,283,284],{},"Object Info > Random"," to a ",[23,287,288],{},"Math > Multiply"," by the number of cells, then to a ",[23,291,292],{},"Math > Floor",", and feed the result into the chain above as ",[119,295,121],{},". In my test, four planes with one shared material got green, blue, blue and red. Random picks repeat, with few objects some pictures may not appear at all, and you cannot choose which object shows what.",[89,298,300],{"id":299},"option-b-a-custom-property-per-object","Option B: a custom property per object",[11,302,303],{},"When you want control, or no repeats:",[46,305,306,328,331],{},[49,307,308,309,312,313,316,317,320,321,324,325,140],{},"Select an object. Open the ",[23,310,311],{},"Object Properties"," tab, ",[23,314,315],{},"Custom Properties"," panel, and press ",[23,318,319],{},"New",". Name it ",[119,322,323],{},"img_index",", type ",[23,326,327],{},"Float",[49,329,330],{},"Type the cell number as the value.",[49,332,333,334,337,338,102,340,236,343,102,346,348,349,352],{},"In the shader add an ",[23,335,336],{},"Attribute"," node, set ",[23,339,160],{},[23,341,342],{},"Object",[23,344,345],{},"Name",[119,347,323],{},", and connect its ",[23,350,351],{},"Fac"," output to the index chain.",[11,354,355],{},"For many objects, set it from the Scripting workspace:",[357,358,363],"pre",{"className":359,"code":360,"language":361,"meta":362,"style":362},"language-python shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","import bpy\nfor i, ob in enumerate(bpy.context.selected_objects):\n    ob[\"img_index\"] = float(i % 4)\n","python","",[119,364,365,373,379],{"__ignoreMap":362},[366,367,370],"span",{"class":368,"line":369},"line",1,[366,371,372],{},"import bpy\n",[366,374,376],{"class":368,"line":375},2,[366,377,378],{},"for i, ob in enumerate(bpy.context.selected_objects):\n",[366,380,382],{"class":368,"line":381},3,[366,383,384],{},"    ob[\"img_index\"] = float(i % 4)\n",[11,386,387],{},"In my test, planes given 3, 0, 2 and 1 showed the cells 3, 0, 2 and 1 of the atlas.",[89,389,391],{"id":390},"option-c-geometry-nodes-instances","Option C: Geometry Nodes instances",[11,393,394],{},"Instances do not have custom properties, but they can carry a named attribute.",[46,396,397,419,442],{},[49,398,399,400,403,404,157,407,102,410,236,412,102,415,418],{},"In your Geometry Nodes tree, after ",[23,401,402],{},"Instance on Points",", add a ",[23,405,406],{},"Store Named Attribute",[23,408,409],{},"Data Type",[23,411,327],{},[23,413,414],{},"Domain",[23,416,417],{},"Instance",". The domain is the thing people miss, because the default is Point.",[49,420,421,422,102,424,426,427,430,431,433,434,437,438,441],{},"Set the ",[23,423,345],{},[119,425,323],{},", and connect ",[23,428,429],{},"Index"," (from the ",[23,432,429],{}," node) to ",[23,435,436],{},"Value",". Use a ",[23,439,440],{},"Math > Modulo"," if you have more instances than images.",[49,443,444,445,447,448,450,451,236,454,456,457,459,460,462],{},"In the shader, add an ",[23,446,336],{}," node with ",[23,449,160],{}," set to ",[23,452,453],{},"Instancer",[23,455,345],{}," ",[119,458,323],{},", and feed its ",[23,461,351],{}," into the same index chain.",[11,464,465,466,469,470,472],{},"The instanced geometry must use that material (a ",[23,467,468],{},"Set Material"," node before Instance on Points). My four instances showed four different cells. For random picks only, ",[23,471,284],{}," also differs per instance, so Option A works on instances without any attribute.",[474,475,476],"blockquote",{},[11,477,478],{},"The Index node follows the order the points were generated, which for a Grid is column by column in my test. To put a specific picture at a specific place, check the order first.",[15,480,482],{"id":481},"method-3-udim-tiles","Method 3: UDIM tiles",[11,484,485,486,236,489,492],{},"A UDIM image has numbered tiles. Tile 1001 is the UV square from 0 to 1, tile 1002 the next square to the right, and so on. You can load files named ",[119,487,488],{},"name.1001.png",[119,490,491],{},"name.1002.png"," as one tiled image.",[11,494,495,496,498,499,502,503,505,506,509],{},"Each object still has to look at its own tile, so the shader is the same job as the atlas: a ",[23,497,156],{}," node whose ",[23,500,501],{},"Location X"," comes from an ",[23,504,336],{}," node. I tested it. With a custom property ",[119,507,508],{},"udim_u"," of 0 or 1 on four planes, they showed tile 1001 and tile 1002 alternately.",[11,511,512],{},"UDIM does not save work here. You still need an index per object, plus one file per tile and the naming convention. It suits one model with several high-resolution texture areas, not a hundred different posters.",[15,514,516],{"id":515},"method-4-an-image-sequence-with-a-frame-offset","Method 4: an image sequence with a frame offset",[11,518,519,520,523],{},"An image sequence is a numbered series of files that Blender steps through by frame. Set the Image Texture node to a sequence and use its ",[23,521,522],{},"Offset"," to shift where each material starts.",[11,525,526],{},"The offset belongs to the node, so every object with that material shares it. I rendered three planes with three materials at offsets 0, 1 and 2 on frame 1 and got three different pictures. That works, but it is Method 1 again: one material per offset. I did not find a stock way to drive the offset per object from one material, so for a different picture per object an atlas is easier.",[15,528,530],{"id":529},"what-goes-wrong","What goes wrong",[532,533,534,540,546,552,561],"ul",{},[49,535,536,539],{},[23,537,538],{},"Pictures look squashed."," A portrait picture in a square cell is stretched. Make the cells the shape of your pictures.",[49,541,542,545],{},[23,543,544],{},"Seams show neighbouring pictures."," Linear filtering reads across cell borders. Leave padding or inset the UVs a pixel or two.",[49,547,548,551],{},[23,549,550],{},"All instances show the same cell."," The named attribute is stored on the Point domain, not Instance, or the shader Attribute node is set to Geometry instead of Instancer.",[49,553,554,557,558,560],{},[23,555,556],{},"Every object shows the first picture."," The Attribute node finds no attribute with that name and returns 0. Check that ",[119,559,323],{}," is spelled the same in the property or Store Named Attribute and in the Attribute node. I tested a misspelled name and a missing property in 4.2.23 and 5.2.2, and all four planes showed cell 0.",[49,562,563,564,140],{},"More fixes are on the ",[565,566,568],"a",{"href":567},"\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting","Image Per Instance troubleshooting page",[15,570,572],{"id":571},"which-method-fits","Which method fits",[574,575,576,592],"table",{},[577,578,579],"thead",{},[580,581,582,586,589],"tr",{},[583,584,585],"th",{},"Method",[583,587,588],{},"Good for",[583,590,591],{},"Breaks when",[593,594,595,607,618,629,640,651],"tbody",{},[580,596,597,601,604],{},[598,599,600],"td",{},"One material per image",[598,602,603],{},"Up to about ten pictures",[598,605,606],{},"Instances, many pictures, later changes",[580,608,609,612,615],{},[598,610,611],{},"Atlas + Object Info Random",[598,613,614],{},"Random look on many objects",[598,616,617],{},"You need a chosen or even spread",[580,619,620,623,626],{},[598,621,622],{},"Atlas + custom property",[598,624,625],{},"Chosen picture per separate object",[598,627,628],{},"Instances, since they have no custom properties",[580,630,631,634,637],{},[598,632,633],{},"Atlas + Store Named Attribute",[598,635,636],{},"Array and Instance on Points",[598,638,639],{},"Needs a Geometry Nodes tree and a shader chain",[580,641,642,645,648],{},[598,643,644],{},"UDIM",[598,646,647],{},"One model with several texture areas",[598,649,650],{},"Many different pictures",[580,652,653,656,659],{},[598,654,655],{},"Image sequence",[598,657,658],{},"Animated or numbered pictures",[598,660,661],{},"Per-object offset on one material",[15,663,665],{"id":664},"faster-with-image-per-instance","Faster with Image Per Instance",[11,667,668,672,673,675],{},[565,669,671],{"href":670},"\u002Faddons\u002Fimage-per-instance","Image Per Instance"," builds the atlas method for you, using the same technique as above. It stores an ",[119,674,323],{}," value (an object custom property on separate objects, and a Store Named Attribute on the Instance domain on instances), and one shared material reads it with an Attribute node. That is the setup you just built by hand.",[11,677,678],{},"What it does in practice:",[46,680,681,694,704],{},[49,682,683,684,173,687,689,690,693],{},"Pick a folder of images in the sidebar tab (",[23,685,686],{},"N",[23,688,671],{},") and press ",[23,691,692],{},"Build Atlas",". The images are packed into one atlas inside the .blend, in file-name order.",[49,695,696,697,700,701,140],{},"Select objects and press ",[23,698,699],{},"Apply To Selected Objects",", or make the object with the Instance on Points or Array modifier active and press ",[23,702,703],{},"Add To Instances (Geometry Nodes)",[49,705,706,707,102,710,713,714,717],{},"Set ",[23,708,709],{},"Order",[23,711,712],{},"Shuffle"," to use every image once before any repeats, and change the ",[23,715,716],{},"Seed"," for another arrangement.",[11,719,720,721,725],{},"It also covers padding between cells, tile shape and fit modes so pictures are not squashed, choosing a picture per object or matching it by object name, and mapping without UVs. The limits (one atlas per file, 16384 px per side) are on the product page, and the steps are in the ",[565,722,724],{"href":723},"\u002Fdocs\u002Fimage-per-instance\u002Fworkflows","Image Per Instance workflows",". It needs Blender 4.2 or newer. The free Image Per Instance Lite builds the atlas and applies it to separate objects, up to 20 images, without Geometry Nodes instances or Shuffle. For a few pictures once, the manual atlas above is free and works.",[727,728,729],"style",{},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":362,"searchDepth":375,"depth":375,"links":731},[732,733,734,741,742,743,744,745],{"id":17,"depth":375,"text":18},{"id":40,"depth":375,"text":41},{"id":83,"depth":375,"text":84,"children":735},[736,737,738,739,740],{"id":91,"depth":381,"text":92},{"id":113,"depth":381,"text":114},{"id":278,"depth":381,"text":279},{"id":299,"depth":381,"text":300},{"id":390,"depth":381,"text":391},{"id":481,"depth":375,"text":482},{"id":515,"depth":375,"text":516},{"id":529,"depth":375,"text":530},{"id":571,"depth":375,"text":572},{"id":664,"depth":375,"text":665},"Give every object, array copy or Geometry Nodes instance its own image in Blender: one material per image, an atlas with UV offsets, UDIM, or a faster add-on.","md",{},true,"\u002Fguides\u002Fdifferent-image-per-instance","\u002Fmedia\u002Fipi.jpg","---\ntitle: \"Different image on each instance in Blender\"\ndescription: \"Give every object, array copy or Geometry Nodes instance its own image in Blender: one material per image, an atlas with UV offsets, UDIM, or a faster add-on.\"\naddon: image-per-instance\nvideo: \u002Fmedia\u002Fipi.mp4\nposter: \u002Fmedia\u002Fipi.jpg\nupdated: 2026-11-16\n---\n\nBlender has no \"image index per object\" input, so one shared material shows one image everywhere. To give each object or instance its own picture, either use one material per image, or pack all images into one atlas and let each object pick its cell through a number the shader can read (an object custom property, or a named attribute stored on a Geometry Nodes instance). The first is fine for a handful of images. The second is the one that scales to dozens, and I ran every step below in Blender 4.2, 4.5 and 5.2.\n\n## Why the obvious node setup only gives colours\n\nThe first thing most people try is **Object Info**. Its **Random** output is a different number from 0 to 1 for every object, and for every Geometry Nodes instance too. Plug it into a **Color Ramp** and each object gets its own colour.\n\nThat is a colour, not a picture. The Image Texture node loads one image and has no socket for \"which image\". Random into a Color Ramp suits randomised tints and stops there. What you need is a number per object that chooses an image.\n\n## Method 1: one material per image\n\nFor a handful of pictures this is the simplest thing that works and needs no node maths.\n\n1. Select the object and open the **Material Properties** tab.\n2. Create a material, add an **Image Texture** node, open the picture and connect **Color** to the **Base Color** of the Principled BSDF.\n3. Duplicate the object (**Shift D**) and give the copy the next material, one object per picture.\n\nIt breaks down when pictures multiply: every new one means a new material and a manual assignment. Instances from Instance on Points or the Array modifier share the material of their source, so they cannot get different pictures this way at all.\n\n## Method 2: an atlas with a UV offset per object\n\nThis is the method that scales. All pictures go into one image laid out in a grid, and the shader shifts the UVs so each object looks at one cell.\n\n### Make the atlas\n\nPut your pictures into a grid of equal cells in any image editor, for example 2 columns by 2 rows for four images, and save one image. Cell 0 is bottom-left, cell 1 is to its right, and rows count upward, because UV space starts at the bottom-left.\n\nSet the Image Texture node's **Interpolation** to **Closest** while you test. With **Linear**, neighbouring cells can bleed into each other at the edges, so leave a few pixels of padding between pictures when you switch it back.\n\n### Build the shader\n\nUse an index number `i` from 0 to the number of cells minus one. For a grid with `cols` columns and `rows` rows, the cell column is `i` modulo `cols` and the row is `floor(i \u002F cols)`.\n\n1. Add **Texture Coordinate** and take its **UV** output into a **Mapping** node. Set **Type** to **Point**.\n2. Set Mapping **Scale** to `1\u002Fcols`, `1\u002Frows`, `1`. For the 2 by 2 atlas that is `0.5`, `0.5`, `1`. This shrinks the UV square to one cell.\n3. Add a **Math** node set to **Floored Modulo** with the second value `cols`. This is the column.\n4. Add a **Math** node set to **Divide** by `cols`, then a **Math** node set to **Floor**. This is the row.\n5. Divide the column by `cols` and the row by `rows` with two more **Math > Divide** nodes, and put the results into **X** and **Y** of a **Combine XYZ** node.\n6. Connect **Combine XYZ** to the **Location** input of the Mapping node.\n7. Connect Mapping **Vector** to the Image Texture **Vector**, and its **Color** to the Principled BSDF **Base Color** (or to an Emission node for a screen).\n\nNow the only missing piece is how the index `i` gets to each object.\n\n### Option A: random index from Object Info\n\nConnect **Object Info > Random** to a **Math > Multiply** by the number of cells, then to a **Math > Floor**, and feed the result into the chain above as `i`. In my test, four planes with one shared material got green, blue, blue and red. Random picks repeat, with few objects some pictures may not appear at all, and you cannot choose which object shows what.\n\n### Option B: a custom property per object\n\nWhen you want control, or no repeats:\n\n1. Select an object. Open the **Object Properties** tab, **Custom Properties** panel, and press **New**. Name it `img_index`, type **Float**.\n2. Type the cell number as the value.\n3. In the shader add an **Attribute** node, set **Type** to **Object** and **Name** to `img_index`, and connect its **Fac** output to the index chain.\n\nFor many objects, set it from the Scripting workspace:\n\n```python\nimport bpy\nfor i, ob in enumerate(bpy.context.selected_objects):\n    ob[\"img_index\"] = float(i % 4)\n```\n\nIn my test, planes given 3, 0, 2 and 1 showed the cells 3, 0, 2 and 1 of the atlas.\n\n### Option C: Geometry Nodes instances\n\nInstances do not have custom properties, but they can carry a named attribute.\n\n1. In your Geometry Nodes tree, after **Instance on Points**, add a **Store Named Attribute** node. Set **Data Type** to **Float** and **Domain** to **Instance**. The domain is the thing people miss, because the default is Point.\n2. Set the **Name** to `img_index`, and connect **Index** (from the **Index** node) to **Value**. Use a **Math > Modulo** if you have more instances than images.\n3. In the shader, add an **Attribute** node with **Type** set to **Instancer** and **Name** `img_index`, and feed its **Fac** into the same index chain.\n\nThe instanced geometry must use that material (a **Set Material** node before Instance on Points). My four instances showed four different cells. For random picks only, **Object Info > Random** also differs per instance, so Option A works on instances without any attribute.\n\n> The Index node follows the order the points were generated, which for a Grid is column by column in my test. To put a specific picture at a specific place, check the order first.\n\n## Method 3: UDIM tiles\n\nA UDIM image has numbered tiles. Tile 1001 is the UV square from 0 to 1, tile 1002 the next square to the right, and so on. You can load files named `name.1001.png` and `name.1002.png` as one tiled image.\n\nEach object still has to look at its own tile, so the shader is the same job as the atlas: a **Mapping** node whose **Location X** comes from an **Attribute** node. I tested it. With a custom property `udim_u` of 0 or 1 on four planes, they showed tile 1001 and tile 1002 alternately.\n\nUDIM does not save work here. You still need an index per object, plus one file per tile and the naming convention. It suits one model with several high-resolution texture areas, not a hundred different posters.\n\n## Method 4: an image sequence with a frame offset\n\nAn image sequence is a numbered series of files that Blender steps through by frame. Set the Image Texture node to a sequence and use its **Offset** to shift where each material starts.\n\nThe offset belongs to the node, so every object with that material shares it. I rendered three planes with three materials at offsets 0, 1 and 2 on frame 1 and got three different pictures. That works, but it is Method 1 again: one material per offset. I did not find a stock way to drive the offset per object from one material, so for a different picture per object an atlas is easier.\n\n## What goes wrong\n\n- **Pictures look squashed.** A portrait picture in a square cell is stretched. Make the cells the shape of your pictures.\n- **Seams show neighbouring pictures.** Linear filtering reads across cell borders. Leave padding or inset the UVs a pixel or two.\n- **All instances show the same cell.** The named attribute is stored on the Point domain, not Instance, or the shader Attribute node is set to Geometry instead of Instancer.\n- **Every object shows the first picture.** The Attribute node finds no attribute with that name and returns 0. Check that `img_index` is spelled the same in the property or Store Named Attribute and in the Attribute node. I tested a misspelled name and a missing property in 4.2.23 and 5.2.2, and all four planes showed cell 0.\n- More fixes are on the [Image Per Instance troubleshooting page](\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting).\n\n## Which method fits\n\n| Method | Good for | Breaks when |\n|---|---|---|\n| One material per image | Up to about ten pictures | Instances, many pictures, later changes |\n| Atlas + Object Info Random | Random look on many objects | You need a chosen or even spread |\n| Atlas + custom property | Chosen picture per separate object | Instances, since they have no custom properties |\n| Atlas + Store Named Attribute | Array and Instance on Points | Needs a Geometry Nodes tree and a shader chain |\n| UDIM | One model with several texture areas | Many different pictures |\n| Image sequence | Animated or numbered pictures | Per-object offset on one material |\n\n## Faster with Image Per Instance\n\n[Image Per Instance](\u002Faddons\u002Fimage-per-instance) builds the atlas method for you, using the same technique as above. It stores an `img_index` value (an object custom property on separate objects, and a Store Named Attribute on the Instance domain on instances), and one shared material reads it with an Attribute node. That is the setup you just built by hand.\n\nWhat it does in practice:\n\n1. Pick a folder of images in the sidebar tab (**N**, **Image Per Instance**) and press **Build Atlas**. The images are packed into one atlas inside the .blend, in file-name order.\n2. Select objects and press **Apply To Selected Objects**, or make the object with the Instance on Points or Array modifier active and press **Add To Instances (Geometry Nodes)**.\n3. Set **Order** to **Shuffle** to use every image once before any repeats, and change the **Seed** for another arrangement.\n\nIt also covers padding between cells, tile shape and fit modes so pictures are not squashed, choosing a picture per object or matching it by object name, and mapping without UVs. The limits (one atlas per file, 16384 px per side) are on the product page, and the steps are in the [Image Per Instance workflows](\u002Fdocs\u002Fimage-per-instance\u002Fworkflows). It needs Blender 4.2 or newer. The free Image Per Instance Lite builds the atlas and applies it to separate objects, up to 20 images, without Geometry Nodes instances or Shuffle. For a few pictures once, the manual atlas above is free and works.\n\n",{"title":5,"description":746},"guides\u002Fdifferent-image-per-instance","2026-11-16","\u002Fmedia\u002Fipi.mp4","ymzHDoZ-AQtQ92lHUzBlryC9kbv16MS3nnFdblJlXqM",{"id":759,"title":760,"blender":761,"body":762,"buy":1049,"description":1056,"extension":747,"lite":1057,"meta":1059,"name":671,"navigation":749,"path":670,"poster":751,"price":1012,"problem":1060,"rawbody":1061,"seo":1062,"status":1063,"stem":1064,"updated":755,"version":1065,"video":756,"__hash__":1066},"addons\u002Faddons\u002Fimage-per-instance.md","Image Per Instance add-on for Blender","4.2 and newer",{"type":8,"value":763,"toc":1039},[764,768,771,777,784,788,825,828,832,881,888,892,903,907,958,964,972,976,979,983,1003,1007],[15,765,767],{"id":766},"the-problem","The problem",[11,769,770],{},"You have forty picture frames, a shelf of book covers or a wall of cards, and each one needs its own image. In Blender a material points at a single image, and the Image Texture node offers no input that says which picture an individual instance should show. The usual ways out are one material per object, which gets heavy fast, or a hand-built texture atlas with a custom attribute and a pile of math nodes that you have to rebuild every time something changes.",[11,772,773,774,776],{},"Image Per Instance builds that setup for you. You point it at a folder, press ",[23,775,692],{},", and every object, array element or Geometry Nodes instance can show a different image while sharing one material.",[11,778,779],{},[780,781],"img",{"alt":782,"src":783},"Before and after in Blender: the same image on every frame, then a different image on each of the 40 frames","\u002Fmedia\u002Fipi-before-after.jpg",[15,785,787],{"id":786},"what-it-does","What it does",[532,789,790,803,808,817],{},[49,791,792,794,795,798,799,802],{},[23,793,692],{}," reads every image in a folder, resizes each one into a tile, and packs them into a single atlas image stored inside your .blend file. The atlas is always in natural file-name order (",[119,796,797],{},"img2"," before ",[119,800,801],{},"img10","), so Image Number 3 is always the third file.",[49,804,805,807],{},[23,806,699],{}," gives each selected mesh its own tile. The image index is stored as a custom property on the object.",[49,809,810,812,813,816],{},[23,811,703],{}," is for Instance on Points, the Array modifier and collection instances. It looks through the host's Geometry Nodes for the objects being instanced (Object Info and Collection Info nodes, including nested groups), puts the shared material on them, and adds a modifier called ",[23,814,815],{},"IPI Assign Index"," to the host. That modifier writes an image number onto every instance, and the material reads it.",[49,818,819,821,822,824],{},[23,820,709],{}," can be \"By file name\" or \"Shuffle\". Shuffle uses every image once before any repeats, and a ",[23,823,716],{}," field gives you other arrangements.",[11,826,827],{},"One material, one atlas, and the material is made of ordinary Blender nodes.",[15,829,831],{"id":830},"beyond-the-basics-full-version","Beyond the basics (full version)",[532,833,834,840,857,863,869,875],{},[49,835,836,839],{},[23,837,838],{},"Tile shape and fit:"," pick a tile shape (1:1, 2:3, 3:2, 3:4, 4:3, 16:9, 9:16) and a fit mode (Stretch, Fit with bars in a colour you choose, or Fill with crop) so pictures are not squashed.",[49,841,842,845,846,849,850,853,854,140],{},[23,843,844],{},"Choose images yourself:"," pick an image by number or by name, or use ",[23,847,848],{},"Match By Object Name"," so an object called ",[119,851,852],{},"poster_cat"," shows ",[119,855,856],{},"cat.png",[49,858,859,862],{},[23,860,861],{},"Material options:"," use image alpha, make the image glow like a screen, set roughness.",[49,864,865,868],{},[23,866,867],{},"Mapping without UVs:"," project from the front, top or side across the whole object.",[49,870,871,874],{},[23,872,873],{},"Animate:"," every object steps through the images every N frames, each starting at its own image.",[49,876,877,880],{},[23,878,879],{},"Random variation:"," shift hue, saturation and brightness per object, and mirror a random half of the objects.",[11,882,883,884,140],{},"Every control is listed in the ",[565,885,887],{"href":886},"\u002Fdocs\u002Fimage-per-instance\u002Fpanel","panel reference",[15,889,891],{"id":890},"what-you-can-use-it-for","What you can use it for",[11,893,894,895,898,899,902],{},"Book spines and covers, posters, paintings and photo frames, cards and tiles, packaging and props, video-wall panels and billboards, and anything scattered or arrayed with Geometry Nodes. Step-by-step recipes are in the ",[565,896,897],{"href":723},"workflows page",", and the guide ",[565,900,901],{"href":750},"different image per instance in Blender"," shows the manual method first.",[15,904,906],{"id":905},"honest-limits","Honest limits",[532,908,909,919,926,933,940,943,955],{},[49,910,911,912,914,915,140],{},"One atlas per .blend file. Pressing ",[23,913,692],{}," again replaces it, and objects keep their pictures by file name. See ",[565,916,918],{"href":917},"\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting#why-did-my-images-change-after-pressing-build-atlas-again","rebuilding the atlas",[49,920,921,922,140],{},"The atlas can be at most 16384 px on each side. For example 256 images at 1024 px fit exactly, 257 do not. See ",[565,923,925],{"href":924},"\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting#what-if-the-atlas-is-too-big-limit-16384","the atlas size limit",[49,927,928,929,140],{},"Front, Top and Side mapping projects straight through the object's bounding box from one direction. Faces that turn away from that direction smear the image into streaks, so give such objects a UV map. See ",[565,930,932],{"href":931},"\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting#why-do-some-faces-look-streaked-with-front-top-or-side-mapping","streaked faces",[49,934,935,936,140],{},"With few images the Shuffle order can show a visible rhythm. See ",[565,937,939],{"href":938},"\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting#why-does-shuffle-look-repetitive","repetitive shuffle",[49,941,942],{},"The image goes on material slot 1 of each object. Other slots stay untouched.",[49,944,945,236,948,950,951,140],{},[23,946,947],{},"Assign Image To Selected",[23,949,848],{}," work on separate objects, not on Geometry Nodes instances. See ",[565,952,954],{"href":953},"\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting#why-does-the-instances-button-say-no-instanced-source-found","no instanced source found",[49,956,957],{},"It is not a replacement for UDIM or texture painting.",[11,959,960,961,140],{},"More cases are covered in ",[565,962,963],{"href":567},"troubleshooting",[11,965,966,967,971],{},"Built and tested by Pavel at Mendbox Studio (",[565,968,970],{"href":969},"\u002Fabout","about",").",[15,973,975],{"id":974},"requirements","Requirements",[11,977,978],{},"Blender 4.2 or newer. The add-on's test scripts run on Blender 4.2.23 LTS, 4.5.14 LTS and 5.2.2 LTS. The add-on is pure Python, needs no internet and no extra software, and is licensed GPL-3.0-or-later.",[15,980,982],{"id":981},"free-lite-version","Free Lite version",[11,984,985,986,236,988,990,991,997,998,1002],{},"Image Per Instance Lite is a separate free download. It has ",[23,987,692],{},[23,989,699],{}," for separate objects, with up to 20 images. Instances, Shuffle, fit modes, assign by name, alpha and emission, mapping without UVs, animation and variation are in the full version only. ",[565,992,996],{"href":993,"rel":994},"https:\u002F\u002Fgithub.com\u002Fmendbox\u002Fimage-per-instance-lite",[995],"nofollow","Get Lite on GitHub",", and see the ",[565,999,1001],{"href":1000},"\u002Fdocs\u002Fimage-per-instance\u002Finstall","install page"," for the differences.",[15,1004,1006],{"id":1005},"how-to-buy","How to buy",[11,1008,1009,1010,1013,1014,1019,1020,1025,1026,1029,1030,1034,1035,140],{},"The full version is ",[23,1011,1012],{},"$12",". Buy it on ",[565,1015,1018],{"href":1016,"rel":1017},"https:\u002F\u002Fquadfix.gumroad.com\u002Fl\u002Fimage-per-instance?utm_source=mendboxstudio&utm_medium=addon-page&utm_campaign=image-per-instance",[995],"Gumroad"," or ",[565,1021,1024],{"href":1022,"rel":1023},"https:\u002F\u002Fsuperhivemarket.com\u002Fproducts\u002Fimage-per-instance?utm_source=mendboxstudio&utm_medium=addon-page&utm_campaign=image-per-instance",[995],"Superhive",", then install the zip in Blender as described in the ",[565,1027,1028],{"href":1000},"install guide",". The ",[565,1031,1033],{"href":1032},"\u002Fdocs\u002Fimage-per-instance","full documentation"," lists every page, including the ",[565,1036,1038],{"href":1037},"\u002Fdocs\u002Fimage-per-instance\u002Fchangelog","changelog",{"title":362,"searchDepth":375,"depth":375,"links":1040},[1041,1042,1043,1044,1045,1046,1047,1048],{"id":766,"depth":375,"text":767},{"id":786,"depth":375,"text":787},{"id":830,"depth":375,"text":831},{"id":890,"depth":375,"text":891},{"id":905,"depth":375,"text":906},{"id":974,"depth":375,"text":975},{"id":981,"depth":375,"text":982},{"id":1005,"depth":375,"text":1006},[1050,1053],{"label":1051,"to":1052},"Buy on Gumroad","https:\u002F\u002Fquadfix.gumroad.com\u002Fl\u002Fimage-per-instance",{"label":1054,"to":1055},"Buy on Superhive","https:\u002F\u002Fsuperhivemarket.com\u002Fproducts\u002Fimage-per-instance","Blender add-on that packs a folder of images into one atlas and gives every object, array element or Geometry Nodes instance its own picture on one material.",{"summary":1058,"to":993},"Free and open source (GPL). Builds the atlas and puts a different image on separate objects, up to 20 images. No Geometry Nodes instances.",{},"How do I put a different image on every object in Blender?","---\ntitle: \"Image Per Instance add-on for Blender\"\ndescription: \"Blender add-on that packs a folder of images into one atlas and gives every object, array element or Geometry Nodes instance its own picture on one material.\"\nname: \"Image Per Instance\"\nprice: \"$12\"\nstatus: released\nproblem: \"How do I put a different image on every object in Blender?\"\nversion: \"0.2.0\"\nblender: \"4.2 and newer\"\nvideo: \u002Fmedia\u002Fipi.mp4\nposter: \u002Fmedia\u002Fipi.jpg\nbuy:\n  - label: \"Buy on Gumroad\"\n    to: \"https:\u002F\u002Fquadfix.gumroad.com\u002Fl\u002Fimage-per-instance\"\n  - label: \"Buy on Superhive\"\n    to: \"https:\u002F\u002Fsuperhivemarket.com\u002Fproducts\u002Fimage-per-instance\"\nlite:\n  summary: \"Free and open source (GPL). Builds the atlas and puts a different image on separate objects, up to 20 images. No Geometry Nodes instances.\"\n  to: \"https:\u002F\u002Fgithub.com\u002Fmendbox\u002Fimage-per-instance-lite\"\nupdated: 2026-11-16\n---\n\n## The problem\n\nYou have forty picture frames, a shelf of book covers or a wall of cards, and each one needs its own image. In Blender a material points at a single image, and the Image Texture node offers no input that says which picture an individual instance should show. The usual ways out are one material per object, which gets heavy fast, or a hand-built texture atlas with a custom attribute and a pile of math nodes that you have to rebuild every time something changes.\n\nImage Per Instance builds that setup for you. You point it at a folder, press **Build Atlas**, and every object, array element or Geometry Nodes instance can show a different image while sharing one material.\n\n![Before and after in Blender: the same image on every frame, then a different image on each of the 40 frames](\u002Fmedia\u002Fipi-before-after.jpg)\n\n## What it does\n\n- **Build Atlas** reads every image in a folder, resizes each one into a tile, and packs them into a single atlas image stored inside your .blend file. The atlas is always in natural file-name order (`img2` before `img10`), so Image Number 3 is always the third file.\n- **Apply To Selected Objects** gives each selected mesh its own tile. The image index is stored as a custom property on the object.\n- **Add To Instances (Geometry Nodes)** is for Instance on Points, the Array modifier and collection instances. It looks through the host's Geometry Nodes for the objects being instanced (Object Info and Collection Info nodes, including nested groups), puts the shared material on them, and adds a modifier called **IPI Assign Index** to the host. That modifier writes an image number onto every instance, and the material reads it.\n- **Order** can be \"By file name\" or \"Shuffle\". Shuffle uses every image once before any repeats, and a **Seed** field gives you other arrangements.\n\nOne material, one atlas, and the material is made of ordinary Blender nodes.\n\n## Beyond the basics (full version)\n\n- **Tile shape and fit:** pick a tile shape (1:1, 2:3, 3:2, 3:4, 4:3, 16:9, 9:16) and a fit mode (Stretch, Fit with bars in a colour you choose, or Fill with crop) so pictures are not squashed.\n- **Choose images yourself:** pick an image by number or by name, or use **Match By Object Name** so an object called `poster_cat` shows `cat.png`.\n- **Material options:** use image alpha, make the image glow like a screen, set roughness.\n- **Mapping without UVs:** project from the front, top or side across the whole object.\n- **Animate:** every object steps through the images every N frames, each starting at its own image.\n- **Random variation:** shift hue, saturation and brightness per object, and mirror a random half of the objects.\n\nEvery control is listed in the [panel reference](\u002Fdocs\u002Fimage-per-instance\u002Fpanel).\n\n## What you can use it for\n\nBook spines and covers, posters, paintings and photo frames, cards and tiles, packaging and props, video-wall panels and billboards, and anything scattered or arrayed with Geometry Nodes. Step-by-step recipes are in the [workflows page](\u002Fdocs\u002Fimage-per-instance\u002Fworkflows), and the guide [different image per instance in Blender](\u002Fguides\u002Fdifferent-image-per-instance) shows the manual method first.\n\n## Honest limits\n\n- One atlas per .blend file. Pressing **Build Atlas** again replaces it, and objects keep their pictures by file name. See [rebuilding the atlas](\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting#why-did-my-images-change-after-pressing-build-atlas-again).\n- The atlas can be at most 16384 px on each side. For example 256 images at 1024 px fit exactly, 257 do not. See [the atlas size limit](\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting#what-if-the-atlas-is-too-big-limit-16384).\n- Front, Top and Side mapping projects straight through the object's bounding box from one direction. Faces that turn away from that direction smear the image into streaks, so give such objects a UV map. See [streaked faces](\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting#why-do-some-faces-look-streaked-with-front-top-or-side-mapping).\n- With few images the Shuffle order can show a visible rhythm. See [repetitive shuffle](\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting#why-does-shuffle-look-repetitive).\n- The image goes on material slot 1 of each object. Other slots stay untouched.\n- **Assign Image To Selected** and **Match By Object Name** work on separate objects, not on Geometry Nodes instances. See [no instanced source found](\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting#why-does-the-instances-button-say-no-instanced-source-found).\n- It is not a replacement for UDIM or texture painting.\n\nMore cases are covered in [troubleshooting](\u002Fdocs\u002Fimage-per-instance\u002Ftroubleshooting).\n\nBuilt and tested by Pavel at Mendbox Studio ([about](\u002Fabout)).\n\n## Requirements\n\nBlender 4.2 or newer. The add-on's test scripts run on Blender 4.2.23 LTS, 4.5.14 LTS and 5.2.2 LTS. The add-on is pure Python, needs no internet and no extra software, and is licensed GPL-3.0-or-later.\n\n## Free Lite version\n\nImage Per Instance Lite is a separate free download. It has **Build Atlas** and **Apply To Selected Objects** for separate objects, with up to 20 images. Instances, Shuffle, fit modes, assign by name, alpha and emission, mapping without UVs, animation and variation are in the full version only. [Get Lite on GitHub](https:\u002F\u002Fgithub.com\u002Fmendbox\u002Fimage-per-instance-lite), and see the [install page](\u002Fdocs\u002Fimage-per-instance\u002Finstall) for the differences.\n\n## How to buy\n\nThe full version is **$12**. Buy it on [Gumroad](https:\u002F\u002Fquadfix.gumroad.com\u002Fl\u002Fimage-per-instance?utm_source=mendboxstudio&utm_medium=addon-page&utm_campaign=image-per-instance) or [Superhive](https:\u002F\u002Fsuperhivemarket.com\u002Fproducts\u002Fimage-per-instance?utm_source=mendboxstudio&utm_medium=addon-page&utm_campaign=image-per-instance), then install the zip in Blender as described in the [install guide](\u002Fdocs\u002Fimage-per-instance\u002Finstall). The [full documentation](\u002Fdocs\u002Fimage-per-instance) lists every page, including the [changelog](\u002Fdocs\u002Fimage-per-instance\u002Fchangelog).\n",{"title":760,"description":1056},"released","addons\u002Fimage-per-instance","0.2.0","54Wmn5jGdlRjQ-6eDveUyo_uk8jHjm5YvLuKUbAr1rk",1794858941689]