nextcloud · skjnldsv · Apr 24, 2026 · Apr 24, 2026
diff --git a/.github/workflows/sphinxbuild.yml b/.github/workflows/sphinxbuild.yml
@@ -340,7 +340,7 @@ jobs:
             --root-dir "$(pwd)/stage"
             --offline --no-progress
             --remap "https://docs.nextcloud.com/server/ file://$(pwd)/stage/"
-            --exclude 'go\.php' --exclude 'mailto:' --exclude-path '.*/404\.html'
+            --exclude 'go\.php' --exclude 'mailto:' --exclude-path '.*/404\.html' --exclude-path '.*/_static/.*'
             --exclude "/user_manual/" --include "/user_manual/en/"
             --exclude '^file://.*/stage/(latest|stable|[0-9]+)/(developer_manual|admin_manual|user_manual)/?$'
             'stage/${{ needs.stage-and-check.outputs.branch_name }}/user_manual/en/**/*.html'

diff --git a/admin_manual/ai/overview.rst b/admin_manual/ai/overview.rst
@@ -118,7 +118,7 @@ Frontend apps
 * `Whiteboard <https://apps.nextcloud.com/apps/whiteboard>`_ integrating Assistant through the smart picker to offer a graphical UI for the various tasks
 * `Deck <https://apps.nextcloud.com/apps/deck>`_ integrating Assistant through the smart picker to offer a graphical UI for the various tasks
 * `Nextcloud Office <https://apps.nextcloud.com/apps/richdocuments>`_ integrating Assistant through the smart picker to offer a graphical UI for the various tasks in documents
-* `Desktop Clients <../../user_manual/desktop/index.rst>`_ for simple "Chat with AI"
+* `Desktop Clients <../../user_manual/desktop/index.html>`_ for simple "Chat with AI"
 
 Backend apps
 ~~~~~~~~~~~~

diff --git a/admin_manual/configuration_database/mysql_4byte_support.rst b/admin_manual/configuration_database/mysql_4byte_support.rst
@@ -13,7 +13,7 @@ installation needs to be tweaked a bit.
 
     This manual only covers MySQL 8 or newer and MariaDB 10.2 or newer.
     If you use MariaDB 10.2, please check
-    `this older version <mysql_4byte_support.rst#mariadb-10-2-or-earlier>`_
+    `this older version <https://docs.nextcloud.com/server/20/admin_manual/configuration_database/mysql_4byte_support.html#mariadb-10-2-or-earlier>`_
     of the documentation. If you use an older version of MySQL or MariaDB, please note that they are no longer supported
     by the current Nextcloud version.
 

diff --git a/admin_manual/configuration_files/big_file_upload_configuration.rst b/admin_manual/configuration_files/big_file_upload_configuration.rst
@@ -45,7 +45,7 @@ relevant php.ini files) ::
 
 The ``upload_max_filesize`` and ``post_max_size`` settings may not apply to file uploads
 through WebDAV single file PUT requests or `Chunked file uploads
-<../../developer_manual/client_apis/WebDAV/chunking.rst>`_
+<../../developer_manual/client_apis/WebDAV/chunking.html>`_
 For those, PHP and webserver timeouts are the limiting factor on the upload size.
 
 Adjust these values for your needs. If you see PHP timeouts in your logfiles,
@@ -160,7 +160,7 @@ Default is ``104857600`` (100 MiB).
 Large file upload on object storage
 -----------------------------------
 
-`Chunked file uploads <../../developer_manual/client_apis/WebDAV/chunking.rst>`_
+`Chunked file uploads <../../developer_manual/client_apis/WebDAV/chunking.html>`_
 do have a larger space consumption on the temporary folder when processing those uploads
 on object storage as the individual chunks get downloaded from the storage and will be assembled
 to the actual file on the Nextcloud servers temporary directory. It is recommended to increase
@@ -172,5 +172,5 @@ enough for PHP, webservers or any load balancers involved.
 Federated Cloud Sharing
 -----------------------
 
-If you are using `Federated Cloud Sharing <federated_cloud_sharing_configuration.rst>`_ and want to share large files, you can increase the timeout values for requests to the federated servers.
+If you are using `Federated Cloud Sharing <federated_cloud_sharing_configuration.html>`_ and want to share large files, you can increase the timeout values for requests to the federated servers.
 Therefore, you can set ``davstorage.request_timeout`` in your ``config.php``. The default value is 30 seconds.
diff --git a/admin_manual/configuration_files/encryption_details.rst b/admin_manual/configuration_files/encryption_details.rst
@@ -346,7 +346,7 @@ Sources
 -------
 
 - `encryption-recovery-tools repository on GitHub <https://github.com/nextcloud/encryption-recovery-tools>`_
-- `Nextcloud Encryption Configuration documentation <encryption_configuration.rst>`_
+- `Nextcloud Encryption Configuration documentation <encryption_configuration.html>`_
 - `Nextcloud Help response concerning the usage of version information <https://help.nextcloud.com/t/allow-file-decryption-with-only-the-files-keys-and-passwords/436/12>`_
 - `Sourcecode: Creation of the Message Authentication Code <https://github.com/nextcloud/server/blob/a374d8837d6de459500e619cf608e0721ea14574/apps/encryption/lib/Crypto/Crypt.php#L504>`_
 - `Sourcecode: Derivation of the Encryption Key <https://github.com/nextcloud/server/blob/a374d8837d6de459500e619cf608e0721ea14574/apps/encryption/lib/Crypto/Crypt.php#L346>`_

diff --git a/admin_manual/configuration_files/external_storage/webdav.rst b/admin_manual/configuration_files/external_storage/webdav.rst
@@ -10,8 +10,8 @@ You need the following information:
 * Folder name: The name of your local mountpoint.
 * The URL of the WebDAV or Nextcloud server.
 * Username and password for the remote server
-* Secure https://: We always recommend https:// for security, though you can 
-  leave this unchecked for http://.
+* Secure ``https://``: We always recommend ``https://`` for security, though you can 
+  leave this unchecked for ``http://``.
 
 Optionally, a ``Remote Subfolder`` can be specified to change the destination
 directory. The default is to use the whole root.

diff --git a/admin_manual/configuration_files/file_sharing_configuration.rst b/admin_manual/configuration_files/file_sharing_configuration.rst
@@ -98,7 +98,7 @@ forcing them.
    <https://github.com/owncloud/core/issues/7009>`_ for discussion of this.
 
 .. note:: There are more sharing options on config.php level available:
-   `Configuration Parameters <../configuration_server/config_sample_php_parameters.rst#sharing>`_
+   `Configuration Parameters <../configuration_server/config_sample_php_parameters.html#sharing>`_
 
 .. _transfer_userfiles_label:
 
@@ -174,7 +174,7 @@ Trashbin contents are not transferred::
 reference.)
 
 Users may also transfer files or folders selectively by themselves.
-See `user documentation <../../user_manual/files/transfer_ownership.rst>`_ for details.
+See `user documentation <../../user_manual/files/transfer_ownership.html>`_ for details.
 
 
 Creating persistent file Shares

diff --git a/admin_manual/configuration_user/profile_configuration.rst b/admin_manual/configuration_user/profile_configuration.rst
@@ -420,5 +420,5 @@ See also
 --------
 
 - :doc:`../configuration_files/file_sharing_configuration` — sharing and autocomplete settings that interact with profile visibility
-- `User manual: Personal settings <../../user_manual/userpreferences.rst>`_ — user-facing profile and personal info settings
+- `User manual: Personal settings <../../user_manual/userpreferences.html>`_ — user-facing profile and personal info settings
 
diff --git a/admin_manual/configuration_user/two_factor-auth.rst b/admin_manual/configuration_user/two_factor-auth.rst
@@ -46,13 +46,13 @@ Other 2FA providers may be found in the App Store.
 .. figure:: ../images/2fa-app-install.png
 
 Developers can also `implement new two-factor provider 
-apps <../../developer_manual/digging_deeper/two-factor-provider.rst>`_.
+apps <../../developer_manual/digging_deeper/two-factor-provider.html>`_.
 
 Enforcing two-factor authentication
 -----------------------------------
 
 By default 2FA is *optional*, hence users are given the choice whether to enable
-it for their account `under their personal settings <../../user_manual/user_2fa.rst>`_.
+it for their account `under their personal settings <../../user_manual/user_2fa.html>`_.
 Admins may, however, enforce the use of 2FA.
 
 Enforcement is possible system-wide (all users) or for selected groups only. Select groups

diff --git a/admin_manual/desktop/index.rst b/admin_manual/desktop/index.rst
@@ -22,5 +22,5 @@ You can find additional information here:
 * `User manual`_
 * `Developer manual`_
 
-.. _`User manual`: ../../user_manual/desktop/index.rst
-.. _`Developer manual`: ../../developer_manual/desktop/index.rst
+.. _`User manual`: ../../user_manual/desktop/index.html
+.. _`Developer manual`: ../../developer_manual/desktop/index.html
diff --git a/admin_manual/index.rst b/admin_manual/index.rst
@@ -25,13 +25,13 @@ For documentation on Nextcloud web, desktop, or mobile clients, see:
 - `Nextcloud User Manual`_
 - `Nextcloud Desktop Client`_
 
-.. _`Nextcloud User Manual`: ../user_manual/index.rst
+.. _`Nextcloud User Manual`: ../user_manual/index.html
 .. _`Nextcloud Desktop Client`: https://docs.nextcloud.com/desktop/latest/
 
 For documentation on development topics, see:
 
 - The individual repositories on GitHub within `the @nextcloud organization <https://github.com/nextcloud/>`_
-- `Nextcloud Development Manual <../developer_manual/index.rst>`_
+- `Nextcloud Development Manual <../developer_manual/index.html>`_
 
 Core Components
 ---------------

diff --git a/admin_manual/installation/example_ubuntu.rst b/admin_manual/installation/example_ubuntu.rst
@@ -14,7 +14,7 @@ following commands in a terminal::
 
 * This installs the packages for the Nextcloud core system. 
   If you are planning on running additional apps, keep in mind that they might
-  require additional packages.  See `Prerequisites for manual installation <source_installation.rst#prerequisites-for-manual-installation>`_ for details.
+  require additional packages.  See `Prerequisites for manual installation <source_installation.html#prerequisites-for-manual-installation>`_ for details.
 
 Now you need to create a database user and the database itself by using the
 MySQL command line interface. The database tables will be created by Nextcloud

diff --git a/admin_manual/installation/harden_server.rst b/admin_manual/installation/harden_server.rst
@@ -302,7 +302,7 @@ Depending on your server setup, these are the possible connections:
 - Any remote Nextcloud server that is connected with federated sharing
 - When downloading apps from the App store other domains might be accessed, based on the choice of the app developers where they host the releases. For all official Nextcloud apps this is not the case though, because they are hosted on Github.
 
-.. _optional (config): ../configuration_server/config_sample_php_parameters.rst#has-internet-connection
+.. _optional (config): ../configuration_server/config_sample_php_parameters.html#has-internet-connection
 .. _detailed field list: https://github.com/nextcloud/survey_client
 
 

diff --git a/admin_manual/issues/general_troubleshooting.rst b/admin_manual/issues/general_troubleshooting.rst
@@ -31,7 +31,7 @@ configuration report with the :ref:`occ config command
 
 .. _the Nextcloud Forums: https://help.nextcloud.com
 .. _FAQ page: https://help.nextcloud.com/t/how-to-faq-wiki
-.. _bugtracker: ../../developer_manual/prologue/bugtracker/index.rst
+.. _bugtracker: ../../developer_manual/prologue/bugtracker/index.html
 
 General troubleshooting
 -----------------------
@@ -411,7 +411,7 @@ does not match the actual data stored in the user's ``data/$userId/files`` direc
 .. note::
 
    Metadata, versions, trashbin and encryption keys are not counted in the used space above.
-   Please refer to the `quota documentation <../../user_manual/files/quota.rst>`_ for details.
+   Please refer to the `quota documentation <../../user_manual/files/quota.html>`_ for details.
 
 Running the following command can help fix the sizes and quota for a given user::
 

diff --git a/admin_manual/occ_apps.rst b/admin_manual/occ_apps.rst
@@ -157,7 +157,7 @@ While setting a configuration value, multiple options are available:
 .. note::
 	See `Appconfig Concepts`_ to learn more about `typed value`, `lazy` and `sensitive` flag.
 
-.. _Appconfig Concepts: ../developer_manual/digging_deeper/config/appconfig.rst#concept-overview
+.. _Appconfig Concepts: ../developer_manual/digging_deeper/config/appconfig.html#concept-overview
 
 You can list all configuration values with one command::
 

diff --git a/admin_manual/occ_files.rst b/admin_manual/occ_files.rst
@@ -336,7 +336,7 @@ The command line option ``--transfer-incoming-shares`` overwrites the config.php
  sudo -E -u www-data php occ files:transfer-ownership --transfer-incoming-shares=0 <source-user> <destination-user>
 
 Users may also transfer files or folders selectively by themselves.
-See `user documentation <../user_manual/files/transfer_ownership.rst>`_ for details.
+See `user documentation <../user_manual/files/transfer_ownership.html>`_ for details.
 
 .. _occ_files_windows_filenames:
 
@@ -427,7 +427,7 @@ Verify your app::
   sudo -E -u www-data php occ integrity:check-app --path=/pathto/app appname
 
 When it returns nothing, your app is signed correctly. When it returns a message then there is an error. See `Code Signing
-<../developer_manual/app_publishing_maintenance/code_signing.rst#how-to-get-your-app-signed>`_ in the Developer manual for more detailed information.
+<../developer_manual/app_publishing_maintenance/code_signing.html#how-to-get-your-app-signed>`_ in the Developer manual for more detailed information.
 
 ``integrity:sign-core`` is for Nextcloud core developers only.
 

diff --git a/admin_manual/office/configuration.rst b/admin_manual/office/configuration.rst
@@ -8,7 +8,7 @@ Nextcloud Office App Settings
 Collabora Online Server
 ***********************
 
-URL (and port) of the Collabora Online server that provides the editing functionality as a WOPI client. Collabora Online should use the same protocol (http:// or https://) as the server installation. Naturally, https:// is recommended.
+URL (and port) of the Collabora Online server that provides the editing functionality as a WOPI client. Collabora Online should use the same protocol (``http://`` or ``https://``) as the server installation. Naturally, ``https://`` is recommended.
 
 Restrict usage to specific groups
 *********************************

diff --git a/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_30.rst b/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_30.rst
@@ -191,7 +191,7 @@ Added APIs
 - ``OCP\Console\ReservedOptions`` was added and contains constants for options reserved for occ core features. ``--debug-log`` and ``--debug-log-level`` are now reserved by occ as they allow to show debug information to the output on any occ command.
 - ``OCP\Security\IHasher::validate()`` should return true if the passed string is a valid hash generated by ``OCP\Security\IHasher::hash()``
 - ``OCP\AppFramework\Http\JSONResponse()`` constructor now supports passing additional ``json_encode`` flags, see https://www.php.net/manual/en/function.json-encode.php for details
-- ``OCP\EventDispatcher\IWebhookCompatibleEvent`` is a new interface for events compatible with webhooks (`see webhook_listeners documentation <../../../admin_manual/webhook_listeners/index.rst>`_).
+- ``OCP\EventDispatcher\IWebhookCompatibleEvent`` is a new interface for events compatible with webhooks (`see webhook_listeners documentation <../../../admin_manual/webhook_listeners/index.html>`_).
 - ``OCP\EventDispatcher\JsonSerializer`` is a new public helper for serializing users and fileinfos to json (ie for webhook events)
 
 Changed APIs
@@ -222,7 +222,7 @@ Changed APIs
 - ``OCP\IUserManager::getDisabledUsers`` now has a third parameter for a search string.
 - ``OCP\User\Backend\IProvideEnabledStateBackend::getDisabledUserList`` now has a third parameter for a search string.
 - Legacy class ``OC_EventSource`` was moved to ``OC`` namespace with the ``OC_`` prefix. It should not change anything if you already correctly use the ``OCP\IEventSourceFactory`` to create these objects.
-- ``OCP\Files\Events\Node\AbstractNodeEvent`` and ``OCP\Files\Events\Node\AbstractNodesEvent`` now implements ``OCP\EventDispatcher\IWebhookCompatibleEvent`` so that all file/folder related events are available for webhooks (`see webhook_listeners documentation <../../../admin_manual/webhook_listeners/index.rst>`_).
+- ``OCP\Files\Events\Node\AbstractNodeEvent`` and ``OCP\Files\Events\Node\AbstractNodesEvent`` now implements ``OCP\EventDispatcher\IWebhookCompatibleEvent`` so that all file/folder related events are available for webhooks (`see webhook_listeners documentation <../../../admin_manual/webhook_listeners/index.html>`_).
 
 Deprecated APIs
 ^^^^^^^^^^^^^^^

diff --git a/developer_manual/basics/logging.rst b/developer_manual/basics/logging.rst
@@ -301,7 +301,7 @@ Admin audit logging
 
 If you want to log things less for system administration but for compliance reasons, e.g. who accessed which file,
 who changed the password of an item or made it public, the
-`admin audit log <../../admin_manual/configuration_server/logging_configuration.rst#admin-audit-log>`_
+`admin audit log <../../admin_manual/configuration_server/logging_configuration.html#admin-audit-log>`_
 is the correct place.
 
 You can easily add a log by simply emitting an ``OCP\Log\Audit\CriticalActionPerformedEvent`` event:

diff --git a/developer_manual/basics/setting.rst b/developer_manual/basics/setting.rst
@@ -110,7 +110,7 @@ The last missing part is to register both classes inside **<myapp>/appinfo/info.
    `<personal>` instead.
 
 Additionally since Nextcloud 23, groups can be granted authorization to access individual
-admin settings (`see admin docs <../../admin_manual/configuration_server/admin_delegation_configuration.rst>`_).
+admin settings (`see admin docs <../../admin_manual/configuration_server/admin_delegation_configuration.html>`_).
 This is a feature that needs to be enabled for each admin setting class.
 To do so, the setting class needs to implement `IDelegatedSettings` instead of `ISettings`
 and implement two additional methods.

diff --git a/developer_manual/client_apis/OCS/ocs-share-api.rst b/developer_manual/client_apis/OCS/ocs-share-api.rst
@@ -225,7 +225,7 @@ Federated Cloud Shares
 ----------------------
 
 Both the sending and the receiving instance need to have federated cloud sharing
-enabled and configured. See `Configuring Federated Cloud Sharing <../../../admin_manual/configuration_files/federated_cloud_sharing_configuration.rst>`_.
+enabled and configured. See `Configuring Federated Cloud Sharing <../../../admin_manual/configuration_files/federated_cloud_sharing_configuration.html>`_.
 
 Create a new Federated Cloud Share
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

diff --git a/developer_manual/desktop/index.rst b/developer_manual/desktop/index.rst
@@ -21,5 +21,5 @@ You can find additional information here:
 * `User manual`_
 * `Admin manual`_
 
-.. _`User manual`: ../../user_manual/desktop/index.rst
-.. _`Admin manual`: ../../admin_manual/desktop/index.rst
+.. _`User manual`: ../../user_manual/desktop/index.html
+.. _`Admin manual`: ../../admin_manual/desktop/index.html
diff --git a/developer_manual/digging_deeper/config/appconfig.rst b/developer_manual/digging_deeper/config/appconfig.rst
@@ -24,7 +24,7 @@ In addition to simple read/write operations, ``IAppConfig`` supports:
 .. note::
    See `Lexicon Concepts`_ to learn more about **Lexicon**, a way to define configuration keys and avoid conflicts in your code.
 
-.. _Lexicon Concepts: lexicon.rst#concept-overview
+.. _Lexicon Concepts: lexicon.html#concept-overview
 
 
 AppFramework

diff --git a/developer_manual/digging_deeper/config/userconfig.rst b/developer_manual/digging_deeper/config/userconfig.rst
@@ -18,7 +18,7 @@ On top of storing and accessing your configuration values, ``IUserConfig`` comes
 .. note::
 	See `Lexicon Concepts`_ to learn more about **Lexicon**, a way to fully define your configuration keys and avoid conflict when using it in your code.
 
-.. _Lexicon Concepts: lexicon.rst#concept-overview
+.. _Lexicon Concepts: lexicon.html#concept-overview
 
 
 Typed Config Values

diff --git a/developer_manual/digging_deeper/context_chat.rst b/developer_manual/digging_deeper/context_chat.rst
@@ -7,8 +7,8 @@ Context Chat
 .. versionadded:: 32.0.0
 
 Nextcloud offers a **Context Chat** API which allows apps like files to submit data
-to the `Nextcloud Assistant Context Chat <../../admin_manual/ai/app_context_chat.rst>`_,
-thereby enabling `Nextcloud Assistant <../../admin_manual/ai/app_assistant.rst>`_
+to the `Nextcloud Assistant Context Chat <../../admin_manual/ai/app_context_chat.html>`_,
+thereby enabling `Nextcloud Assistant <../../admin_manual/ai/app_assistant.html>`_
 to answer questions, provide insights and search results based on the submitted data and natural language queries.
 
 Implementing a content provider for Context Chat

diff --git a/developer_manual/exapp_development/faq/DockerSocketProxy.rst b/developer_manual/exapp_development/faq/DockerSocketProxy.rst
@@ -28,7 +28,7 @@ Nextcloud AIO implements its own `Docker Socket Proxy container <https://github.
 you just need to tick the checkbox in the AIO configuration interface to enable it.
 AppAPI automatically creates the default Deploy daemon configuration for Nextcloud AIO.
 
-See `Nextcloud in Docker AIO (all-in-one) <../../../admin_manual/exapps_management/DeployConfigurations.rst#nextcloud-in-docker-aio-all-in-one>`_ for more details.
+See `Nextcloud in Docker AIO (all-in-one) <../../../admin_manual/exapps_management/DeployConfigurations.html#nextcloud-in-docker-aio-all-in-one>`_ for more details.
 
 .. note::
 

diff --git a/developer_manual/exapp_development/faq/Troubleshooting.rst b/developer_manual/exapp_development/faq/Troubleshooting.rst
@@ -27,7 +27,7 @@ Here are some common steps to verify the network configuration:
 ExApp deployment issues
 -----------------------
 
-The deployment issues questions are covered in the `Test Deploy <../../../admin_manual/exapps_management/TestDeploy.rst>`_ section of the administration guide.
+The deployment issues questions are covered in the `Test Deploy <../../../admin_manual/exapps_management/TestDeploy.html>`_ section of the administration guide.
 Generally speaking, there are three steps to find the proper error message to understand the problem:
 
 1. Check Nextcloud logs

diff --git a/developer_manual/exapp_development/tech_details/Translations.rst b/developer_manual/exapp_development/tech_details/Translations.rst
@@ -43,7 +43,7 @@ You can then compile them to ``.mo`` files using `ui_example's <https://github.c
 Manual install
 **************
 
-For the ``manual-install`` type, an administrator will have to manually extract to the server's `writable apps directory <../../../admin_manual/configuration_server/config_sample_php_parameters.rst#apps-paths>`_ ``l10n`` folder of the ExApp
+For the ``manual-install`` type, an administrator will have to manually extract to the server's `writable apps directory <../../../admin_manual/configuration_server/config_sample_php_parameters.html#apps-paths>`_ ``l10n`` folder of the ExApp
 (e.g. ``/path/to/apps-writable/<appid>/l10n/*.(js|json)``).
 This will allow the server to access the ExApp's strings with translations.