How To Batch-Replace Smart Objects in Photoshop: Create Mockup Images In Bulk!

Learn how to batch-replace Smart Objects in Photoshop! You can automate mockup image creation, using PSD mockup templates, to generate all your mockups in bulk. This detailed Photoshop tutorial will show you how.
Learn more here: "Batch-Replace Smart Objects: Mockups In Bulk" -- Photoshop Plugin: exchange.adobe.com/apps/cc/8e...

[@YouShouldAutomateThat]

You can add this plugin to Photoshop by installing it here: exchange.adobe.com/apps/cc/8e3097ba/batch-replace-smart-objects

[@YouShouldAutomateThat]

UPDATE: v1.0.18 (and above) of our plugin now officially supports: 1) the batch-replacement of multiple different Smart Objects in the same mockup scene, and 2) PNG export for your final images. Regarding mockups with multiple Smart Objects, simply ensure that your target Smart Object layers are selected/highlighted in the layer stack, and the plugin will operate on them accordingly during the operations. For PNG export, simply select that as your preference when you set up/save operations.

[@ci2own]

I'm thiking on buying this plugin, and i wonder if it will make exactly what i need: I have a .psd of a two sides box, and every side is an smart object (One is Front Box, and other is Box Spine). I also have one folder with images for Front Box (A.png, B.png, C.png, etc.) and another folder for the Box Spines with the same names (A.png, B.png, C.png). Would this plugin be able to get Box Front A.png and Box Spine A.png, place them on its respective smart object, and export the results for all images? Thanks in advance. (And the same for the rest of the images B.png, C.png, etc?)

[@YouShouldAutomateThat]

It's tricky in your case since you want to batch-replace different Smart Objects in the same mockup scene with **different images**. Version 1.0.17 of the plugin (which will be available within the next few days) and above will support batch-replacing multiple Smart Objects in the same PSD file simultaneously -- BUT it uses the same image for each one. So basically as it iterates through all the images in the Input Folder, you'll be able to just have whatever Smart Object layers you want to replace highlighted/selected in the layer stack, and it'll automatically replace all of those Smart Objects with the current image. This is more for situations where like, there would be 3 identical soda cans in different spots of a mockup scene where you want the same label applied to them, or 3 different business cards on a table where you want the same logo applied to them, etc.
By contrast, what you're describing is much more complicated and isn't the sort of thing that's amenable to standardizing into the plugin -- definitely not in a way that's easy to use / user-friendly. The only way to set it up to handle every possible scenario of "what specific folder/image(s) you want to use for each specific smart object in each PSD file" would be to add tons of complex branching options that would make the plugin seem painfully complicated to use, especially for the 99% of users who are just creating basic mockups. Like for each operation you'd have to specify what specific Smart Object, with what name or in what position in the layer stack, you want to correspond to what different Input Folder. And that's assuming you want to iterate sequentially through cleanly separated Input Folders whose filenames map onto one another perfectly. Others users might have different folder setups , different "sequence of actions they want the plugin to perform" requirements, like one single folder with images named "1.png", "2.png", "3.png", where they want to iterate through the one folder, but batch-replace using groups of 3 images to create matching wall-art sets or something like that. That's kind of what I mean when I say, trying to push it to be this complex really makes it hard to actually standardize the product and set it up for those complicated operations.
One thing many users tell us they really like about our plugin is how simple and easy to use it is. It's therefore pretty unlikely that we're going to add lots of very complex branching options that would only be utilized in maybe 1-2% of cases. I wish I had better news or could have been more helpful on this, I'm just trying to give you the honest answer as to the limitations of the plugin and the realistic ability to automate certain tasks in a user-friendly way within the plugin.

[@hexxl0r]

please add .png for output and .pdf for input

[@YouShouldAutomateThat]

PNG export is now officially available in v1.0.18 (and above) of our plugin. Thank you for the feature suggestion!