# dcc.Markdown Display Local Images **URL:** \ **Category:** Dash Python\ **Created:** [April 13, 2022, 7:29am UTC](https://community.plotly.com/t/dcc-markdown-display-local-images/63006 "2022-04-13T07:29:44Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![davidharris](https://avatars.discourse-cdn.com/v4/letter/d/df705f/32.png) [@davidharris](https://community.plotly.com/u/davidharris)\ **Post date:** [June 22, 2024, 11:18am UTC](https://community.plotly.com/t/dcc-markdown-display-local-images/63006/3 "2024-06-22T11:18:21Z")
There is an (undocumented?) option to specify a different local assets path app = dash.Dash(assets\_folder=…) > [@\[Sharing insights\] Using assets\_folder for apps where the assets folder is not in the root of the project](https://community.plotly.com/t/sharing-insights-using-assets-folder-for-apps-where-the-assets-folder-is-not-in-the-root-of-the-project/14263): > > I haven’t been this documented, so I thought it was worth to share with others. If you, like I do, want to have your project structure with something similar to this: myproject ├── bin ├── MANIFEST.in ├── myproject │ ├── app.py │ ├── assets │ ├── init.py │ └── main.py ├── README.md ├── setup.py └── tests and you run it through python myproject/app.py or python -m myproject; You will find that the assets/ folder is not served automatically by Dash as it is explained [here](https://dash.plot.ly/external-resources). … --- _[View the full topic](https://community.plotly.com/t/dcc-markdown-display-local-images/63006)._