# Podcasts integration into webinterface

**URL:** <https://discourse.mopidy.com/t/podcasts-integration-into-webinterface/5983>\
**Category:** Help and support\
**Created:** [July 18, 2024, 8:19am UTC](https://discourse.mopidy.com/t/podcasts-integration-into-webinterface/5983 "2024-07-18T08:19:40Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![TX9G9qBxid](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/tx9g9qbxid/32/2512_2.png) [@TX9G9qBxid](https://discourse.mopidy.com/u/TX9G9qBxid)\
**Post date:** [July 18, 2024, 8:19am UTC](https://discourse.mopidy.com/t/podcasts-integration-into-webinterface/5983/1 "2024-07-18T08:19:40Z")

</div>

Hi,

I’m trying to figure out how to integrate my podcast library into Mopidy and have been looking at the Mopidy-Podcast extension.

I can’t however figure out whether the only way to integrate the separate podcasts is to have them get organized together with My Music collection?  
Does anyone know if it is possible to have a “Podcasts” list item e.g. in the left hand web interface menu that only shows my podcasts. Or do I need to have all music and podcast presented in the “Album” and “Tracks” list items under “My Music”?

This last method of mixing music and podcasts seems a bit strange to me.

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [July 18, 2024, 8:35am UTC](https://discourse.mopidy.com/t/podcasts-integration-into-webinterface/5983/2 "2024-07-18T08:35:35Z")

</div>

Mopidy treats podcasts just like any other audio and it doesn’t get a dedicated Podcast section. Some clients do treat some extensions differently with special features and you might find one that treats Mopidy-Podcast differently and exposes it as you want. I don’t know of any such client.

However, if your client supports Mopidy’s browsing interface then you should find a section where each extension is broken out separately and presented like a filesystem. That would be the best way to use something like Mopidy-Podcast.

---

<div class="post-metadata">

**Author:** ![TX9G9qBxid](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/tx9g9qbxid/32/2512_2.png) [@TX9G9qBxid](https://discourse.mopidy.com/u/TX9G9qBxid)\
**Post date:** [July 19, 2024, 6:13pm UTC](https://discourse.mopidy.com/t/podcasts-integration-into-webinterface/5983/4 "2024-07-19T18:13:19Z")

</div>

Thanks for the answer, though it is a shame it is not possible at present.

I’ll see if I can find my way around to the feature request section and make a post - or support an existing one. I believe dedicated sections for music and podcasts are important.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [July 20, 2024, 9:45pm UTC](https://discourse.mopidy.com/t/podcasts-integration-into-webinterface/5983/5 "2024-07-20T21:45:09Z")

</div>

Best of luck. But like I said, I think most people are served just fine by the virtual filesystem browsing interface. Your feature would ideally explain why that doesn’t suffice .

---

<div class="post-metadata">

**Author:** ![TX9G9qBxid](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/tx9g9qbxid/32/2512_2.png) [@TX9G9qBxid](https://discourse.mopidy.com/u/TX9G9qBxid)\
**Post date:** [July 21, 2024, 8:59am UTC](https://discourse.mopidy.com/t/podcasts-integration-into-webinterface/5983/6 "2024-07-21T08:59:32Z")

</div>

Good feedback. Will make sure to emphasize that.

---

<div class="post-metadata">

**Author:** ![system](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/system/32/1_2.png) [@system](https://discourse.mopidy.com/u/system)\
**Post date:** [July 24, 2024, 9:00am UTC](https://discourse.mopidy.com/t/podcasts-integration-into-webinterface/5983/7 "2024-07-24T09:00:23Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.