# IPFS File Naming Tools

**URL:** <https://discuss.ipfs.tech/t/ipfs-file-naming-tools/9170>\
**Category:** Ecosystem and Usage\
**Created:** [September 30, 2020, 12:43pm UTC](https://discuss.ipfs.tech/t/ipfs-file-naming-tools/9170 "2020-09-30T12:43:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![yeehi](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/yeehi/32/2760_2.png) [@yeehi](https://discuss.ipfs.tech/u/yeehi)\
**Post date:** [September 30, 2020, 12:43pm UTC](https://discuss.ipfs.tech/t/ipfs-file-naming-tools/9170/1 "2020-09-30T12:43:04Z")

</div>

People may wish to make their content available through IPFS hash and also through HTTP on a website for example.

What tools are available which, when the file is created, both generate an IPFS hash and allocate it to the file alongside a human readable file name?

Here are two examples:

If somebody creates a video file which they wish to publish on the Internet using both IPFS and HTTP, at the moment the file is first saved to disk, a name for the file will be requested, and at the same time, an IPFS hash will be generated and somehow incorporated into the file name. Something like this:

FunnyCatVideo.Qm123456789abcdefghijk.mkv

Example 2:  
Somebody has many funny cat videos saved to their disk. All the videos have sensible names but nothing indicating their IPFS hash:  
FunnyCat1.mkv  
FunnyCat2.mkv  
FunnyCat3. mkv  
FunnyCat4.mkv  
and the unforgettable  
FunnyCat5.mkv

The plan is to upload these videos to the internet. IPFS Desktop rapidly allocates all the files an IPFS hash, and publishes them on IPFS. What is missing is that on the webpage where people come to look at the cat videos, there is no indication that the file is also available via IPFS. Visitors just see the HTML file name. It would require repetitive, manual filename renaming to incorporate the IPFS hash, or the addition of a file description field, which would include the IPFS hash, which doesn’t integrate the filename with the hash.

---

<div class="post-metadata">

**Author:** ![Akita](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/akita/32/2650_2.png) [@Akita](https://discuss.ipfs.tech/u/Akita)\
**Post date:** [September 30, 2020, 5:11pm UTC](https://discuss.ipfs.tech/t/ipfs-file-naming-tools/9170/2 "2020-09-30T17:11:14Z")

</div>

I think you can indicate the IPFS availability with some HTTP header wizardry. I can’t remember which one, though.  
And the client (browser, etc) have to understand the hint and act accordingly, of course.

---

<div class="post-metadata">

**Author:** ![Akita](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/akita/32/2650_2.png) [@Akita](https://discuss.ipfs.tech/u/Akita)\
**Post date:** [September 30, 2020, 5:17pm UTC](https://discuss.ipfs.tech/t/ipfs-file-naming-tools/9170/3 "2020-09-30T17:17:30Z")

</div>

Here is a potential way for doing that:

> <https://github.com/ipfs/in-web-browsers/issues/144>
>
> Alt-Svc is an Internet Standard (RFC7838) which allow an origin's resources to be authoritatively available at a separate network location, possibly...

Another one is to include it in the file’s metadata, I guess.

---

<div class="post-metadata">

**Author:** ![yeehi](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/yeehi/32/2760_2.png) [@yeehi](https://discuss.ipfs.tech/u/yeehi)\
**Post date:** [September 30, 2020, 5:33pm UTC](https://discuss.ipfs.tech/t/ipfs-file-naming-tools/9170/4 "2020-09-30T17:33:38Z")

</div>

Akita, this is exactly what I wanted! That software is top quality by the look of it, very well considered. It handles IPNS and TOR too. Thank you very much!

More people should become familiar with Alt-Svc.