"The diff for this file is too large to render" - Can the limit be increased?

When trying to display the diff of a (long) file in a commit, I get "The diff for this file is too large to render." instead of the diff.

- What is the upper limit of the file size that Stash is still willing to display?

- Is there a way to increase this limit?

3 answers

1 accepted

This widget could not be displayed.


Stash applies two limits to diff rendering to limit memory usage:

# Maximum length for any line returned from a given file when viewing source. This value truncates long lines. There is no mechanism for retrieving the truncated part short of downloading the entire file.


# Maximum number of segment lines (of any type, total) which may be returned for a single diff. Unlike other page limits, this is a hard limit; subsequent pages cannot be requested when a diff exceeds this size.


Both settings can be overridden in STASH_HOME/stash-config.properties. You'll need to restart Stash to pick up the updated configuration.

Does anyone know where this setting is for Bitbucket server 4.1? That file doesn't seem to exist (also checked replacing the stash with bitbucket)

It's now called bitbucket.properties and should be created in BITBUCKET_HOME/shared/

Thanks i found it where you suggested!

This widget could not be displayed.

Hi Balazs,

Could this help you out?


Best regards,


I found this myself as well. That question is about the number of files in a pull request, i have a problem with the number of lines in one file. So I guess it doesn't solve my problem.

That won't work; that settings defines the limit of the number of changes (path elements) that's renderable in a pull request.

This widget could not be displayed.

Does anyone have a good feel for the impact on system performance if we increase the defaults by a factor of 10?

It depends quite much on how many users are doing what exactly. If large diffs are relatively rare compared to all the other things the server does, it will not have a significant performance impact. Try for an hour or a day and keep track of the performance indicators of the server.

(I did increase this by a factor of 10 to to 50k. We have so many users, and so few huge diffs that it did not really make a difference in the performance.)

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted 7 hours ago in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

13 views 0 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you