> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/getting-started/managing-photos-videos-and-illustrations/connecting-photos-and-videos-to-use-in-your-report.md). # Connecting Photos and Videos to Use in Your Report This first video shows how you can use media from the gallery of your mobile device and share it with ScribeWare and how you can also take media from ScribeWare and back it up on your mobile device. {% embed url="" %} ## This next video shows how to merge media from your computer into ScribeWare. This is perfect for sewer scopes and drone media that are imported from a memory card. {% embed url="" %} This is also perfect if you use a point-and-shoot camera or want to include infrared images or chimney scans. {% endembed %} ## This last video shows how media can be used when taken in the ScribeWare mobile application. This is generally the fastest way to use media in ScribeWare. Note that media will be auto-synched to all devices in your account with access to a given report. --- # 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.scribeware.com/getting-started/managing-photos-videos-and-illustrations/connecting-photos-and-videos-to-use-in-your-report.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.