# Documentation inconsistency - how to set chunk size?

**URL:** <https://help.nextcloud.com/t/documentation-inconsistency-how-to-set-chunk-size/207989>\
**Category:** ℹ️ Support\
**Created:** [October 28, 2024, 9:18pm UTC](https://help.nextcloud.com/t/documentation-inconsistency-how-to-set-chunk-size/207989 "2024-10-28T21:18:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tessus](https://help.nextcloud.com/user_avatar/help.nextcloud.com/tessus/32/7607_2.png) [@tessus](https://help.nextcloud.com/u/tessus)\
**Post date:** [October 28, 2024, 9:18pm UTC](https://help.nextcloud.com/t/documentation-inconsistency-how-to-set-chunk-size/207989/1 "2024-10-28T21:18:24Z")

</div>

The link [Uploading big files \> 512MB — Nextcloud latest Administration Manual latest documentation](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html#adjust-chunk-size-on-nextcloud-side) shows:

* * *

Adjust chunk size on Nextcloud side

For upload performance improvements in environments with high upload bandwidth, the server’s upload chunk size may be adjusted:

```auto
sudo -u www-data php occ config:app:set files max_chunk_size --value 20971520

```

* * *

but [Configuration Parameters — Nextcloud latest Administration Manual latest documentation](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/config_sample_php_parameters.html#files-chunked-upload-max-size) shows:

* * *

files.chunked\_upload.max\_size

```auto
'files.chunked_upload.max_size' => 100 * 1024 * 1024,

```

* * *

So which one is it? Or are both valid and what happens if you set them to different valus?

Basically what do I actually have to set when I want to set the chunk size for uploads on the server?

---

<div class="post-metadata">

**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/6_22734026db12803ebb3e059622ac3534.png) [@jtr](https://help.nextcloud.com/u/jtr)\
**Post date:** [October 29, 2024, 12:36pm UTC](https://help.nextcloud.com/t/documentation-inconsistency-how-to-set-chunk-size/207989/2 "2024-10-29T12:36:32Z")

</div>

> [@tessus](#):
>
> So which one is it? Or are both valid and what happens if you set them to different valus?

Your reading the docs for the upcoming v31 release. There are some changes happening for a new generation of chunk handling across the clients. That second config value is part of that.

The `max_chunk_size` is an older parameter that adjusts the max chunk size for the Web client. It’s the only parameter that you’ll find active in any published release.

> Basically what do I actually have to set when I want to set the chunk size for uploads on the server?

In published releases, the chunk size is set on the clients themselves.

---

<div class="post-metadata">

**Author:** ![tessus](https://help.nextcloud.com/user_avatar/help.nextcloud.com/tessus/32/7607_2.png) [@tessus](https://help.nextcloud.com/u/tessus)\
**Post date:** [October 29, 2024, 7:49pm UTC](https://help.nextcloud.com/t/documentation-inconsistency-how-to-set-chunk-size/207989/3 "2024-10-29T19:49:03Z")

</div>

> [@jtr](#):
>
> The `max_chunk_size` is an older parameter that adjusts the max chunk size for the Web client. It’s the only parameter that you’ll find active in any published release.

Thanks.

> [@jtr](#):
>
> In published releases, the chunk size is set on the clients themselves.

I suppose you mean all clients, except the web client. If you really mean all clients including the web client, the parameter is obsolete and not used no matter what and the parameter should be removed from the documentation.

In fact the documentation should include your info by default.

---

<div class="post-metadata">

**Author:** ![spyro](https://help.nextcloud.com/letter_avatar/spyro/32/6_22734026db12803ebb3e059622ac3534.png) [@spyro](https://help.nextcloud.com/u/spyro)\
**Post date:** [November 26, 2024, 11:18pm UTC](https://help.nextcloud.com/t/documentation-inconsistency-how-to-set-chunk-size/207989/4 "2024-11-26T23:18:45Z")

</div>

The upcoming release 31 sounds like it might finally solve the upload problem for me - am I to understand that the new release will force clients to use a specified chunk size?

Right now, unless I want to set nginx’s client\_max\_body\_size to (frankly) nutty values, I have to also force all the clients (linux desktop, web, android client) to use a value below client\_max\_body\_size. This would be fine - except that I can’t find any way to set the web or android clients chunk size.

Is there any “wisdom from on high” that the NC royalty feel like bestowing on us?

---

<div class="post-metadata">

**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\
**Post date:** [February 24, 2025, 11:18pm UTC](https://help.nextcloud.com/t/documentation-inconsistency-how-to-set-chunk-size/207989/5 "2025-02-24T23:18:53Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.