• Max attachment size
• Repository size limit
  • How it works
• Troubleshooting
  • 413 Request Entity Too Large

Account and limit settings

Max attachment size

You can change the maximum file size for attachments in comments and replies in GitLab. Navigate to Admin Area (wrench icon) > Settings > General, then expand Account and Limit. From here, you can increase or decrease by changing the value in Maximum attachment size (MB).

Repository size limit

Repositories within your GitLab instance can grow quickly, especially if you are using LFS. Their size can grow exponentially, rapidly consuming available storage.

To avoid this from happening, you can set a hard limit for your repositories’ size. This limit can be set globally, per group, or per project, with per project limits taking the highest priority.

There are numerous use cases where you might set up a limit for repository size. For instance, consider the following workflow:

1. Your team develops apps which require large files to be stored in the application repository.
2. Although you have enabled Git LFS to your project, your storage has grown significantly.
3. Before you exceed available storage, you set up a limit of 10 GB per repository.

How it works

Only a GitLab administrator can set those limits. Setting the limit to 0 means there are no restrictions.

These settings can be found within:

• Each project’s settings.
• A group’s settings.
• The Size limit per repository (MB) field in the Account and limit section of a GitLab instance’s settings by navigating to either:
  • Admin Area > Settings > General.
  • The path /admin/application_settings.

The first push of a new project, including LFS objects, will be checked for size and will be rejected if the sum of their sizes exceeds the maximum allowed repository size.

Note: The repository size limit includes repository files and LFS, and does not include artifacts.

For details on manually purging files, see reducing the repository size using Git.

Troubleshooting

413 Request Entity Too Large

If you are attaching a file to a comment or reply in GitLab and receive the 413 Request Entity Too Large error, it is likely caused by having a max attachment size larger than what the web server is configured to allow.

If you wanted to increase the max attachment size to 200m in a GitLab Omnibus install, for example, you might need to add the line below to /etc/gitlab/gitlab.rb before increasing the max attachment size:

nginx['client_max_body_size'] = "200m"