# Can read from a mounted folder but cannot write to it

**URL:** <https://forum.inductiveautomation.com/t/can-read-from-a-mounted-folder-but-cannot-write-to-it/112271>\
**Category:** Ignition\
**Tags:** ignition81, scripting, perspective\
**Created:** [November 19, 2025, 2:11pm UTC](https://forum.inductiveautomation.com/t/can-read-from-a-mounted-folder-but-cannot-write-to-it/112271 "2025-11-19T14:11:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [November 19, 2025, 2:11pm UTC](https://forum.inductiveautomation.com/t/can-read-from-a-mounted-folder-but-cannot-write-to-it/112271/1 "2025-11-19T14:11:18Z")

</div>

I am running Perspective in v8.1.42 and I have a web dev mounted folder that I can read from but I cannot write to it.

I want to know if this behavior is a permissions issue?

The web dev mountedFolder is linked to the following:

```python
/var/ignition/Photos/
```

and I can read from that location just fine - for example

```python
/system/webdev/projectName/mountedFolder/image.png
```

This is the code that actually works. Both options actually indicate success which tells me Ignition thinks it is writing somewhere when using the mountedFolder path below.

```python
pathBase = "/var/ignition/Photos/" #<-- this works
# pathBase = "/system/webdev/projectName/mountedFolder/" #<-- does not work

newPath = pathBase + "image.png"

dest = File(newPath)

parent = dest.getParentFile()
if not parent.exists():
    parent.mkdirs()

event.file.copyTo(dest)
```

I have no issue setting an image component source property to either of the options presented above indicating I do have read permissions available.

Any input is appreciated.

---

<div class="post-metadata">

**Author:** ![Kevin\_Flener](https://avatars.discourse-cdn.com/v4/letter/k/74df32/32.png) [@Kevin\_Flener](https://forum.inductiveautomation.com/u/Kevin_Flener)\
**Post date:** [November 19, 2025, 2:49pm UTC](https://forum.inductiveautomation.com/t/can-read-from-a-mounted-folder-but-cannot-write-to-it/112271/2 "2025-11-19T14:49:42Z")

</div>

> [@bmeyers](#):
>
> ```python
> pathBase = "/var/ignition/Photos/" #<-- this works
> # pathBase = "/system/webdev/projectName/mountedFolder/" #<-- does not work
> 
> newPath = pathBase + "/image.png"
> 
> ```

You have a forward slash at both the end of the base, and the beginning of the “/image.png”.  
If this isn’t a typo, it could be lending itself to your problem.

You get:” …/Photos//image.png”

I use full UNC file paths when writing to a webdev mounted folder on a shared network drive.  
example: ‘//NetworkHostName/ShareName/Folder/Folder/Folder/’

---

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [November 19, 2025, 2:58pm UTC](https://forum.inductiveautomation.com/t/can-read-from-a-mounted-folder-but-cannot-write-to-it/112271/3 "2025-11-19T14:58:25Z")

</div>

Good catch but it was just a typo on my end. I took out some of the details when making the post here.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 19, 2025, 4:33pm UTC](https://forum.inductiveautomation.com/t/can-read-from-a-mounted-folder-but-cannot-write-to-it/112271/4 "2025-11-19T16:33:48Z")

</div>

> [@bmeyers](#):
>
> `/system/webdev/projectName/mountedFolder/image.png`

This URL like path would happen to evaluate to a real path on Unix-ey systems - literally the path pictured. It doesn't surprise me that Ignition thinks it can write there, though it would slightly surprise me if you actually can write to that path.

---

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [November 19, 2025, 5:54pm UTC](https://forum.inductiveautomation.com/t/can-read-from-a-mounted-folder-but-cannot-write-to-it/112271/5 "2025-11-19T17:54:19Z")

</div>

You nailed it. Ignition creates that path and writes the file to it.
