> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/ios/portfolios.md). # Portfolios - [Create PDF portfolio or package on iOS](https://docs.apryse.com/ios/portfolios/portfolio.md): Create a dynamic PDF portfolio with various file types assembled into an integrated PDF. Learn how to create a PDF portfolio and showcase your work effectively. The Apryse iOS SDK streamlines secure d - [Create a PDF portfolio (package) on iOS](https://docs.apryse.com/ios/portfolios/create.md): Learn how to create a PDF portfolio with multiple file types using this code sample. Explore how to create, extract, and manipulate PDF Packages efficiently. The Apryse iOS SDK streamlines secure docu - [Sample to create PDF packages on iOS](https://docs.apryse.com/ios/portfolios/samples.md): Learn how to create, extract, and manipulate PDF Packages (Portfolios) with this sample. Enhance your PDF skills now! The Apryse iOS SDK streamlines secure document processing and seamlessly integrate - [APIs for creating PDF packages on iOS](https://docs.apryse.com/ios/portfolios/apis.md): Discover utility classes for portfolios with PDF documents in iOS using Objective-C/Swift. Learn about PTPDFDoc and enhance your app functionalities today! The Apryse iOS SDK streamlines secure docume --- # 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.apryse.com/ios/portfolios.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.