# Extending character limit beyond 99000

**URL:** https://meta.discourse.org/t/extending-character-limit-beyond-99000/143381
**Category:** Feature
**Created:** [March 5, 2020, 7:59am UTC](https://meta.discourse.org/t/extending-character-limit-beyond-99000/143381 "2020-03-05T07:59:50Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Tim\_Jefferies](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tim_jefferies/32/113296_2.png) [@Tim\_Jefferies](https://meta.discourse.org/u/Tim_Jefferies)
#### Post date: [March 5, 2020, 7:59am UTC](https://meta.discourse.org/t/extending-character-limit-beyond-99000/143381/1 "2020-03-05T07:59:50Z")

</div>

I realise that for most usage cases this isn’t going to be useful, but I was wondering :

- Why 99000 specifically? Is it technical limitation?
- Can we raise that value further as an admin (with a message explaining any consequences)?

I’m running 2 discourse instances, one is a private wiki and the other is a public forum. People have hit this limit in both.  
It is possible to seperate the topic post in to seperate replies yes, but its not ideal to do this - and crucially for the wiki renders the DiscoTOC; automatic table of contents plugin unusable (Which is exactly what we need for long wikis).

Finally. Is there a way that I can delve into the docker image and override this setting if it can’t be raised as part of the discourse code?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 5, 2020, 9:40am UTC](https://meta.discourse.org/t/extending-character-limit-beyond-99000/143381/2 "2020-03-05T09:40:55Z")

</div>

The largest consequence of raising this too high is that cooking markdown can get pretty expensive on enormous documents.

The limit is kind of arbitrary, I do not think anything would explode in fire if you raised it to 200k or 300k in a very controlled environment.

The only clean way to override this line: [discourse/config/site\_settings.yml at 3610709b6cf859f674a02394f1430bb51f68d117 · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/3610709b6cf859f674a02394f1430bb51f68d117/config/site_settings.yml#L636-L636) is in a custom plugin. The upside is that the plugin is kind of trivial.

I have seen requests once or twice to raise our “max” limit, but it certainly is not a common request.

---

<div class="post-metadata">

### Author: ![Tim\_Jefferies](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tim_jefferies/32/113296_2.png) [@Tim\_Jefferies](https://meta.discourse.org/u/Tim_Jefferies)
#### Post date: [March 5, 2020, 9:48am UTC](https://meta.discourse.org/t/extending-character-limit-beyond-99000/143381/3 "2020-03-05T09:48:14Z")

</div>

Unfortunately I have never written a line of ruby code in my life, so I have no idea how to do that. Sys admin stuff easy peasy, but coding leaves me queasy.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 5, 2020, 9:49am UTC](https://meta.discourse.org/t/extending-character-limit-beyond-99000/143381/4 "2020-03-05T09:49:59Z")

</div>

I reckon someone could build this plugin for you in about 1 hour, so a budget of $50-$200 on #Marketplace would land you this change easily.

I strongly don’t recommend forking here for the change this will place your forums at great long term risk, container hacking is going to break web updates.
