# Custom Domain for HF Spaces
**URL:**
**Author:**  [@Oltion](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FOltion)%5C
**Post date:** [July 23, 2022, 11:11am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcustom-domain-for-hf-spaces%2F20761%2F1 "2022-07-23T11:11:42Z")
Is it possible to use a custom domain instead of the one provided by HF Spaces?
Thanks!
---
**Author:**  [@clem](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fclem)%5C
**Post date:** [August 2, 2022, 3:15pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcustom-domain-for-hf-spaces%2F20761%2F2 "2022-08-02T15:15:09Z")
We’re thinking of maybe building this. To make sure we build it the right way, why do you want a custom domain?
---
**Author:**  [@Oltion](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FOltion)%5C
**Post date:** [August 2, 2022, 3:56pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcustom-domain-for-hf-spaces%2F20761%2F3 "2022-08-02T15:56:35Z")
Well, because HF Spaces are way faster in terms of computation compared to other providers (at least the cheap options). There is no comparison.
In my case, I have a MVP which makes some similarity computations based on the user input, though I don’t use any HF model. So, it will be cool show my MVP on a custom domain.
In addition, it’s extremely fast in terms of deployment process which allows me to make many experimentations. Another provider (whose name I am not going to provide here) takes about 15 minutes to deploy from the github push.
Hope I replied to your question. 😉
---
**Author:**  [@ambITious](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FambITious)%5C
**Post date:** [December 28, 2022, 6:27am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcustom-domain-for-hf-spaces%2F20761%2F4 "2022-12-28T06:27:54Z")
yes please add custom domain option.
---
**Author:**  [@chrka](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fchrka)%5C
**Post date:** [May 23, 2023, 10:47pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcustom-domain-for-hf-spaces%2F20761%2F5 "2023-05-23T22:47:53Z")
yes
please custom domains
i would love to run my project through ur spaces.
still learning, also it seems for now the simplest way to deploy code, test it life with my team and at the same time sharing it with the public
---
**Author:**  [@silvaKenpachi](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FsilvaKenpachi)%5C
**Post date:** [May 27, 2023, 12:17pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcustom-domain-for-hf-spaces%2F20761%2F6 "2023-05-27T12:17:44Z")
any progress on custom domains
---
**Author:**  [@rjviswha](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Frjviswha)%5C
**Post date:** [August 6, 2023, 10:58am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcustom-domain-for-hf-spaces%2F20761%2F7 "2023-08-06T10:58:32Z")
Hi,
Any updates regarding custom domain ??
---
**Author:**  [@freddyaboulton](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Ffreddyaboulton)%5C
**Post date:** [August 6, 2023, 3:17pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcustom-domain-for-hf-spaces%2F20761%2F8 "2023-08-06T15:17:55Z")
No updates on this as far as I’m aware. Cc @julien-c @victor
---
**Author:**  [@rjviswha](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Frjviswha)%5C
**Post date:** [August 7, 2023, 6:48pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcustom-domain-for-hf-spaces%2F20761%2F11 "2023-08-07T18:48:39Z")
nope, that’s not working, getting permission error
---
**Author:**  [@jglowa](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fjglowa)%5C
**Post date:** [October 1, 2025, 3:43am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcustom-domain-for-hf-spaces%2F20761%2F12 "2025-10-01T03:43:18Z")
Now Hugging Face Spaces allow [custom domain](https://huggingface.co/docs/hub/spaces-custom-domain) in PRO and Team or Enterprise subscriptions.
But there is a free workaround: you can embed a full-page `