# Image Path Using Google Shared Drive **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [July 11, 2025, 3:18pm UTC](https://forum.inductiveautomation.com/t/image-path-using-google-shared-drive/108378 "2025-07-11T15:18:06Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 11, 2025, 3:25pm UTC](https://forum.inductiveautomation.com/t/image-path-using-google-shared-drive/108378/2 "2025-07-11T15:25:30Z")
If you're willing to run some separate out of process python programs to support this then the easiest approach might be to just serve the images up over HTTP using Python's built in HTTP server. > [@Recommended Approach for Displaying Third Party Images](https://forum.inductiveautomation.com/t/recommended-approach-for-displaying-third-party-images/40588/11): > > If these machines will have Python 3 installed you can start a simple HTTP server like this: python -m http.server -b localhost -d /path/to/images I suppose since this is Vision you'd want to bind that HTTP server to 0.0.0.0 instead of localhost so it was reachable by all the clients. Otherwise every Vision PC needs to run all the python programs and access the images locally. --- _[View the full topic](https://forum.inductiveautomation.com/t/image-path-using-google-shared-drive/108378)._