> For the complete documentation index, see [llms.txt](https://docs.boostfordaz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.boostfordaz.com/using-boost-for-daz/rendering-with-boost-for-daz/rendering-the-daz-project/same-file-multiple-renders.md).

# Same File Multiple Renders

While uploading the render ‘package’ (.duf file and enhancement elements) for the first time - and as long as you remain connected to the same active session - Boost for Daz enhances an intelligent caching feature in Iray Server that automatically creates a temporary cache in the cloud of the entire package for you. So after you view your first completed render and you go back and make changes to your Daz project and hit ‘render’ again, only the updates are collected in a smaller ‘package’ and sent up to the active Iray Server session on Boost for Daz. The updates and all the previous files and elements (now stored in this temporary cache) are used to create your new render output. So as long as you are connected to the same Iray server session on Boost for Daz, the second and all subsequent renders will take significantly less time. As soon as you sign out, that session is disassembled and all temporary caches are deleted (ephemeral).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.boostfordaz.com/using-boost-for-daz/rendering-with-boost-for-daz/rendering-the-daz-project/same-file-multiple-renders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.