# Custom Teable URL

**URL:** https://community.teable.ai/t/custom-teable-url/205
**Category:** Feature Requests
**Tags:** cloud
**Created:** [April 20, 2026, 4:24am UTC](https://community.teable.ai/t/custom-teable-url/205 "2026-04-20T04:24:33Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![ankush.thor](https://community.teable.ai/user_avatar/community.teable.ai/ankush.thor/32/268_2.png) [@ankush.thor](https://community.teable.ai/u/ankush.thor)
#### Post date: [April 20, 2026, 4:24am UTC](https://community.teable.ai/t/custom-teable-url/205/1 "2026-04-20T04:24:33Z")

</div>

## What’s the feature?

Ability to Customise the teable subdomain URL

## Your use case

For Internal apps if we don’t want to connect a subdomain, having a nice to read teable subdomain would be nice.

---

<div class="post-metadata">

### Author: ![Leo](https://community.teable.ai/user_avatar/community.teable.ai/leo/32/78_2.png) [@Leo](https://community.teable.ai/u/Leo)
#### Post date: [April 20, 2026, 5:26am UTC](https://community.teable.ai/t/custom-teable-url/205/2 "2026-04-20T05:26:39Z")

</div>

Hi @ankush.thor ,

Thanks for sharing this request. The use case is clear, especially for internal apps where a custom domain may be unnecessary but a cleaner Teable subdomain would still be helpful. We’ll give this some thought on our side.

---

<div class="post-metadata">

### Author: ![Leo](https://community.teable.ai/user_avatar/community.teable.ai/leo/32/78_2.png) [@Leo](https://community.teable.ai/u/Leo)
#### Post date: [April 21, 2026, 8:54am UTC](https://community.teable.ai/t/custom-teable-url/205/3 "2026-04-21T08:54:46Z")

</div>

Hi @ankush.thor,

Update: We’ve added this to our roadmap. Stay tuned to our changelog for updates.
