> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/8.5/user-guide/decompiler/batch.md). # Batch operation The decompiler supports the batch mode operation with the text and GUI versions of IDA. All you need is to specify the -Ohexrays switch in the command line. The format of this switch is: ``` -Ohexrays:-option1:-option2:outfile:func1:func2\... ``` The valid options are: * **-new** decompile only if output file does not exist * **-nosave** do not save the database (idb) file after decompilation * **-errs** send problematic databases to hex-rays.com * **-lumina** use Lumina server * **-mail=** your email (meaningful if **-errs** option is used) The output file name can be prepended with **+** to append to it. If the specified file extension is invalid, **.c** will be used. The functions to decompile can be specified by their addresses or names. The **ALL** keyword means all non-library functions. For example: ``` idat -Ohexrays:-errs:-mail=john@mail.com:outfile:ALL -A input ``` will decompile all nonlibrary functions to **outfile.c**. In the case of an error, the **.idb** file will be sent to **hex-rays.com**. The -A switch is necessary to avoid the initial dialog boxes. --- # 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://docs.hex-rays.com/8.5/user-guide/decompiler/batch.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.