> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-faq/using-the-software/files/large-project-files.md). # Large Project Files Why ENERCALC Project Files grow large and how to shrink them by removing saved reports. ## Why are my ENERCALC Project Files so large? The current version of the ENERCALC Project File format was designed to hold a tremendous amount of information and to be very flexible for future enhancements. One item that Project Files hold is the complete printout for each calculation in the project. Because each printout can span multiple pages and contain sketches and stress diagrams, it can consume a lot of space. If file size becomes an issue, you can use a function to purge a Project File of all its saved reports. The command is **Tools** > **Remove saved reports from project file**. Use it with caution, because it does what it says. Once you remove saved reports from a Project File, you can regenerate them using **File** > **Regenerate Reports**, but the process takes a few minutes to complete. However, we want you to know that we're rather obsessed with optimizing program and data file size and speed. We will continually work to refine the way our new file format is used to reduce size requirements through eliminating unneeded information, using data compression, and applying other approaches. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://enercalc.com/docs/sel-faq/using-the-software/files/large-project-files.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.