# Feature Request - Resursive "Import cover from file" script

**URL:** https://community.mp3tag.de/t/feature-request-resursive-import-cover-from-file-script/66501
**Category:** General Discussion
**Created:** [November 11, 2024, 3:19pm UTC](https://community.mp3tag.de/t/feature-request-resursive-import-cover-from-file-script/66501 "2024-11-11T15:19:31Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [November 11, 2024, 3:35pm UTC](https://community.mp3tag.de/t/feature-request-resursive-import-cover-from-file-script/66501/4 "2024-11-11T15:35:30Z")

</div>

I don't know how often in the life of a file a cover has to be imported from such varying paths.  
So I would think that simply an action group with 2 (or more) actions that import covers from various folder depths would be a good way.  
... and that such a folder is

> [@ethrusio](#):
>
> usually called /Artwork

does not seem to be true as the linked thread looks for covers in

> [@Cover Problem (Cover einfügen) ab v2.51](https://community.mp3tag.de/t/cover-problem-cover-einfugen-ab-v2-51/13443/5):
>
> ..\Cover\Front-small.jpg

I see in your suggestion the problem that you would have to switch on an off that recursion if you want to get the desired hits if you have several picture files in different folder depths.  
And if you do that, you could alternatively adapt the path ...

So I think until your request becomes a feature, there are a number of workarounds

---

_[View the full topic](https://community.mp3tag.de/t/feature-request-resursive-import-cover-from-file-script/66501)._