# Forking native WeWeb components to use as Coded Components

**URL:** <https://community.weweb.io/t/forking-native-weweb-components-to-use-as-coded-components/20183>\
**Category:** Developer corner\
**Created:** [October 16, 2025, 3:05pm UTC](https://community.weweb.io/t/forking-native-weweb-components-to-use-as-coded-components/20183 "2025-10-16T15:05:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Artur.AppDaHorta](https://avatars.discourse-cdn.com/v4/letter/a/ed655f/32.png) [@Artur.AppDaHorta](https://community.weweb.io/u/Artur.AppDaHorta)\
**Post date:** [October 16, 2025, 3:05pm UTC](https://community.weweb.io/t/forking-native-weweb-components-to-use-as-coded-components/20183/1 "2025-10-16T15:05:20Z")

</div>

WeWeb keeps releasing and improving its native components over time, and many of them are great.

However, every now and then we run into some **limitations** with these components. In those cases, it would be extremely useful to be able to **“fork” a native component** and use it as the base for a **Coded Component**.

This would allow us to:

- Reuse the entire structure and design already built by WeWeb,

- Make only the necessary adjustments (e.g., adding extra functionality, customizing behaviors, or changing interactions),

- Avoid the heavy work of rebuilding a component from scratch — which often involves replicating design settings, layout, styles, and more.

I couldn’t find a way to do this directly through the editor.  
Is there any **official or alternative way** to fork a native component — maybe through GitHub or another method — so we can build on top of it instead of starting from zero?

---

<div class="post-metadata">

**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\
**Post date:** [October 16, 2025, 3:30pm UTC](https://community.weweb.io/t/forking-native-weweb-components-to-use-as-coded-components/20183/2 "2025-10-16T15:30:46Z")

</div>

Hi Artur 👋

You can fork almost any element, you just need to click on the 3 dots and \> Fork component

 ![Screenshot 2025-10-16 at 12.29.54](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/4/4009cc60f963ccd219fe2fc1e60f760a69f04c2a.png)

---

<div class="post-metadata">

**Author:** ![Artur.AppDaHorta](https://avatars.discourse-cdn.com/v4/letter/a/ed655f/32.png) [@Artur.AppDaHorta](https://community.weweb.io/u/Artur.AppDaHorta)\
**Post date:** [October 16, 2025, 6:52pm UTC](https://community.weweb.io/t/forking-native-weweb-components-to-use-as-coded-components/20183/3 "2025-10-16T18:52:38Z")

</div>

Wow, I totally missed that “Fork component” option 😄  
Thanks a lot for pointing it out — super helpful!