An image inserted in a text project can disappear when the relationship between the manuscript and image changes. The safe sequence is to identify every referring manuscript before the move, let the path change follow the move, and then verify both sides: the new relative path exists and the old one no longer does.
Count from the manuscript, not from the picture
Suppose chapters/C03.md contains . The starting point is the chapters folder that contains C03, so the path climbs one level and enters images. If the picture moves to assets/maps/map.png, the manuscript must point to ../assets/maps/map.png.
A ten-chapter project may use the same map in three files. A careful manual approach searches the workspace for the exact old target, records the referring files and occurrences, moves the asset, and edits only the destinations inside Markdown link syntax. A broad replacement of the text map.png can alter prose or a different file with a similar name.
Why a Finder-only move often creates extra work
Moving the image first feels efficient until a preview shows an empty frame. Once the original hierarchy has been forgotten, it is easy to connect the chapter to the wrong picture. Duplicate the project or preserve a recoverable source before reorganizing. Inspect the image itself as well; path correctness cannot tell a map from a chart.
Web links beginning with https: and page fragments are outside this local relationship. They should not be swept into a path cleanup. The same caution applies to proprietary markup or document types that the editor does not recognize.
Move through Rune Studio's project controls
Open the project folder as a workspace and locate chapters/C03.md and images/map.png in Rune Studio's file tree. Use the file information or Quick Look view to confirm the asset. When an in-use target is moved or deleted, review the reported number of referring files and occurrences before accepting the operation. Then move it with the file tree or the integrated file browser.
The current Mac application updates relative targets in Markdown image and link syntax inside txt, text, md, and markdown files. Open tabs are updated, while closed manuscripts retain their source encoding during the rewrite. A path recorded as an EPUB cover can follow the asset as well. These are bounded behaviors, not a promise to rewrite every link-like string in every format.
In a one-manuscript, one-image trial, the source lookup found one referring file and one occurrence. After the image moved, one reference was rewritten and the manuscript reopened with the new relative path present. That result demonstrates the supported case. It does not assess image quality or broaden the rule to external URLs.
Search backward after the move
A working preview in chapter three does not prove that chapter seven is clean. Search for the complete old path and require no unexplained results. Then search for the new target and compare the results with the pre-move inventory. Finally, open the picture to ensure the correct asset was connected.
If the new path is absent, restore the image before continuing. If old references remain, inspect closed files and unsupported extensions instead of repeatedly moving the asset. If a web URL changed, undo that edit and repeat the operation with the local Markdown destination precisely selected.
File organization is complete when you can state which manuscripts point to which new location and why no stale path remains. Try the procedure on a one-image copy before reorganizing a production book. Rune Studio's supported formats and exclusions are described on its current Mac product page.
