# Penpot bug report on text rendering overrides

**URL:** <https://community.penpot.app/t/penpot-bug-report-on-text-rendering-overrides/10460>\
**Category:** Help us improve Penpot\
**Tags:** bug\
**Created:** [March 28, 2026, 2:21pm UTC](https://community.penpot.app/t/penpot-bug-report-on-text-rendering-overrides/10460 "2026-03-28T14:21:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![IvanTheGeek](https://avatars.discourse-cdn.com/v4/letter/i/8c91f0/32.png) [@IvanTheGeek](https://community.penpot.app/u/IvanTheGeek)\
**Post date:** [March 28, 2026, 2:21pm UTC](https://community.penpot.app/t/penpot-bug-report-on-text-rendering-overrides/10460/1 "2026-03-28T14:21:25Z")

</div>

Plugin/API-created component instances keep stored text overrides, but canvas and export render master text

I found a tighter Penpot repro that looks like a real bug, and I’m opening a GitHub issue for it.

Short version:

- create real component instances from library assets
- update text on the instance
- the updated text is present in the live shape data
- but the canvas and export still render the master/default text

So this seems to be a render / override-application problem, not just a bad plugin write.

I’m using this in a local Event Modeling workflow, but the issue seems more general than that.

GitHub issue:  
[[#8826]](https://github.com/penpot/penpot/issues/8826)