> For the complete documentation index, see [llms.txt](https://guide.onionmobile.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.onionmobile.dev/tor-on-ios/arti-and-onionmasq-on-ios.md). # Arti and Onionmasq on iOS Currently, Arti on mobile is still quite experimental and not actively maintained. The features it already has can be tried out on iOS with either using [Arti Mobile Experimental](https://gitlab.com/guardianproject/arti-mobile-ex) directly, or by using it embedded in [Tor.framework](https://github.com/iCepa/Tor.framework), which gives you the advantage of having some helper classes at hand. There's a [Podspec](https://github.com/iCepa/Tor.framework/blob/pure_pod/Arti.podspec), which supports that. In your `Podfile:` ```ruby pod 'Tor/Arti', :podspec => 'https://github.com/iCepa/Tor.framework/blob/pure_pod/Arti.podspec' ``` Said `Podspec` also contains an experimental version of [OnionMasq](https://gitlab.torproject.org/tpo/core/onionmasq), which contains Arti + IP packet routing (so you can use it on a `tun` device or Apple's [Network Extension API](https://developer.apple.com/documentation/networkextension) directly). At some point in the future this will probably replace the C-Tor + IPtProxy + leaf combination, which Orbot iOS currently uses. --- # 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://guide.onionmobile.dev/tor-on-ios/arti-and-onionmasq-on-ios.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.