First off, renaming “Screenshot” to “Render” is a great change. It’s much clearer and far more accurate regarding the output quality.
However, the UI changes introduced in this update significantly disrupt our daily workflow and slow us down:
Loss of Default Save Location: Having to manually relocate the save directory for every single render adds unnecessary friction. The system should remember the last used folder or default path.
External File Naming Issue: Forcing us to name the render outside of the system File Explorer is a major step backward. In design iteration workflows (V1, V2, V3, etc.), clicking an existing file in the Explorer window to overwrite or update the version number is standard practice. The new flow makes versioning tedious and prone to human error.
These changes directly impact our productivity and introduce unnecessary error sources into a routine process.
Please consider bringing back the option to save directly through the native File Explorer with a persistent path.
Regarding the default save location: this is definitely still possible in Enscape 4.19. You can set a Default Folder location in the Visual Settings’ Output tab. If there is a default folder specified there, it will automatically be populated as the folder location in the Render window. If you are experiencing other behavior when setting a Default Folder, please do let me know so we can investigate further.
Please note that there is currently a regression regarding the system remembering the last folder used. If you have a Default Folder set, and manually change the export location to a different folder in the Render window, the next time you open the Render window, the Default Folder location will be shown again, instead of the changed export location. Our developers are working to change this back to the behavior that the window would remember the last used folder if you change it away from the Default Folder.
Regarding the external file naming: at this point it is not planned to directly bring back the File Explorer window selection via the Render window. However, there is a trick to still accessing the File Explorer: if you trigger the render export using a hotkey, this will automatically open the File Explorer for saving, instead of the Render window. So if you prefer to save via the File Explorer, the workaround is to stick to the hotkey export. By default, the hotkey is set to [SHIFT + F11], but you can set your own in the Enscape Window Settings‘ Input tab.
Very bad news for Enscape users: instead of improving rendering quality, your team is focusing on changing the interface, forcing users to relearn Enscape repeatedly. It’s extremely frustrating.
Thank you for sharing your feedback as well. We understand that changes to the interface can be frustrating. At the same time, we hope the new export flows provide an improvement over the previous experience.
It would be very valuable for our Product Managers to understand which aspects of the changes are causing the most frustration for you. If you’re able to share some specific examples of what you find most problematic, we’d be happy to pass that feedback on to the relevant team.
Screenshot naming has become my biggest headache lately. I just can’t see why workarounds are suddenly necessary. Everything used to run smoothly in the previous version. Why fix what was never broken, especially when it has worked perfectly since Enscape’s very first release? I’ve been a loyal user since 2018.
You mentioned: "Regarding the external file naming: at this point it is not planned to directly bring back the File Explorer window selection via the Render window. "
Another issue has cropped up with the Enscape viewport in version 4.19. I depend on perfectly matching the Enscape and SketchUp viewports when exporting screenshots, so I can seamlessly layer everything in Photoshop during post-production.
Enscape’s smooth integration with SketchUp is the main reason I keep coming back for quick renders. Still, when I compare it to D5, Enscape falls short in offering control over materials, lighting, entourage, vegetation, and animation.
@dario_dimauro thanks for the feedback - I will certainly pass it along to our PMs. In regards to the view sync issue: this is a bug in 4.19. Our developers are already investigating it and hope to deliver a fix in the next release of Enscape. If it is deeply hindering your workflow in the meantime, you can of course switch back to Enscape 4.18, where the issue is not present.
@maarten_wijnen Indeed, as I mentioned previously, the fact that it doesn’t work like this is a regression. In the next version of Enscape, the window would remember the last used folder, whether or not you have a Default Folder defined.
the shift+f11 workflow sucks, but I’m happy it exists. Thanks for your help!
Nevertheless, I think you guys should consider to change the save-render-process back to where it was, it is obviously not thought through an has major design flaws (I don’t mean the bugs).
Thanks for sticking with this thread — the detail you’ve given is genuinely useful.
One thing caught my attention. Shift+F11 gives you back the File Explorer save flow, which is roughly what you had before 4.19, and you still describe it as bad. That makes me think reverting to the old flow might not actually get you what you want, and I’d rather find out what would than just put the old window back.
So, two questions:
When you use the hotkey route, what specifically makes it painful? Is it that it bypasses the Render window and its settings, or was the Explorer save already a hassle in its own right?
Imagine the save step worked exactly how you’d want it to for a V1/V2/V3 iteration cycle — what happens when you hit export? Where does the file go, what’s it called, and how much do you have to type?
No need for anything polished, a rough description of how you’d want it to behave is exactly what helps.
I think oit should be a single, streamlined export window that provides immediate access to all essential output settings without requiring navigation through sub-menus or the general Visual Settings dialogue.
1. Render Mode Selection
Toggle between Single Render and Batch Rendering directly within the export window.
2. Output Destination
Display a file path field that defaults to the last used folder.
Keep the quick-export workflow (like the current Shift + F11 behavior) to open the file explorer and save directly without extra steps.
3. Flexible File Naming Rules
Custom Naming & Suffixes: Option to define a base name with automatic incremental version tags (e.g., _V1, _V2).
Prefix Customization: An option to disable the default automatic timestamp prefix (e.g., Enscape_2026-08-18-…) or replace it with a user-defined custom prefix. (Manually renaming dozens of batch-rendered files afterwards creates unnecessary friction.)
4. File Format
Dropdown to select the output format (.png, .jpg, etc.) directly before exporting.
5. Output Resolution
Quick-select presets (720p, 1080p, 4K, Custom) right inside the dialogue, eliminating the need to modify resolution inside the general Render/Visual Settings.
I have to do multiple versions of rendering, so want to see how many version already that I have rendered in files explorer → Click lates file (MMT_FACADE DESIGN_OP 1) → Keep full name, change only last option number (MMT_FACADE DESIGN_OP 2) → done
For this current method, if do it correctly as dev intention. I have to write all full name of the file each time before render?
Suggestion, would be useful if we could use scenes name as files name.