TYPO3-Documentation · linawolf · Apr 4, 2026 · Apr 4, 2026
diff --git a/Documentation/Administration/ExtensionManagement/ClassicMode/Index.rst b/Documentation/Administration/ExtensionManagement/ClassicMode/Index.rst
@@ -79,7 +79,7 @@ of it, you can uninstall / install extensions manually with
 Uninstall / Deactivate Extension via TYPO3 Backend
 --------------------------------------------------
 
-..  include:: /Images/AutomaticScreenshots/ExtensionManager/UninstallExtension.rst.txt
+..  include:: /Images/ManualScreenshots/ExtensionManager/UninstallExtension.rst.txt
 
 
 Log into the TYPO3 Backend and open the module

diff --git a/Documentation/Administration/Installation/ComposerMode/Index.rst b/Documentation/Administration/Installation/ComposerMode/Index.rst
@@ -273,7 +273,7 @@ issues it has detected accompanied by a resolution for each issue.
 Once changes have been made, TYPO3 can re-scan the host environment by reloading
 the page :samp:`https://example-project-site.local/typo3/install.php`.
 
-..  include:: /Images/AutomaticScreenshots/QuickInstall/Step1SystemEnvironment.rst.txt
+..  include:: /Images/ManualScreenshots/QuickInstall/Step1SystemEnvironment.rst.txt
 
 ..  _install-select-db:
 
@@ -282,7 +282,7 @@ Select a database
 
 Select a database connection driver and enter the credentials for the database.
 
-..  include:: /Images/AutomaticScreenshots/QuickInstall/Step2DatabaseConnection.rst.txt
+..  include:: /Images/ManualScreenshots/QuickInstall/Step2DatabaseConnection.rst.txt
 
 TYPO3 can either connect to an existing empty database or create a new one.
 
@@ -293,7 +293,7 @@ For example, if an instance of TYPO3 is intended to be used with a MySQL databas
 Once it is installed, :guilabel:`MySQL Database` will be available as an option.
 
 
-..  include:: /Images/AutomaticScreenshots/QuickInstall/Step3ChooseDb.rst.txt
+..  include:: /Images/ManualScreenshots/QuickInstall/Step3ChooseDb.rst.txt
 
 ..  _install-create-admin:
 
@@ -304,7 +304,7 @@ An administrator account needs to be created to gain access to TYPO3's backend.
 
 An email address for this user can also be specified and a name can be given.
 
-..  include:: /Images/AutomaticScreenshots/QuickInstall/Step4AdminUserSitename.rst.txt
+..  include:: /Images/ManualScreenshots/QuickInstall/Step4AdminUserSitename.rst.txt
 
 ..  note::
     The password must comply with the configured
@@ -322,7 +322,7 @@ Beginners should
 select the first option and allow TYPO3 to create an empty starting page.
 This will also generate a site configuration file.
 
-..  include:: /Images/AutomaticScreenshots/QuickInstall/Step5LastStep.rst.txt
+..  include:: /Images/ManualScreenshots/QuickInstall/Step5LastStep.rst.txt
 
 ..  _install-ddev:
 

diff --git a/Documentation/Administration/Troubleshooting/TYPO3.rst b/Documentation/Administration/Troubleshooting/TYPO3.rst
@@ -38,15 +38,15 @@ using the following address to create a new administrative user:
 The Install Tool requires the "Installation Password" that would have been set
 when TYPO3 was installed.
 
-.. include:: /Images/AutomaticScreenshots/InstallTool/InstallToolPassword.rst.txt
+.. include:: /Images/ManualScreenshots/InstallTool/InstallToolPassword.rst.txt
 
 Once logged in to the Admin Tool go to :guilabel:`Maintenance > Create Administrative User`
 and select :guilabel:`Create Administrator`. In this dialogue you
 can create a new administrative user.
 
-.. include:: /Images/AutomaticScreenshots/BackendUsers/CreateAdministrator.rst.txt
+.. include:: /Images/ManualScreenshots/BackendUsers/CreateAdministrator.rst.txt
 
-.. include:: /Images/AutomaticScreenshots/BackendUsers/CreateAdministratorForm.rst.txt
+.. include:: /Images/ManualScreenshots/BackendUsers/CreateAdministratorForm.rst.txt
 
 Use this new administrator account to log into the TYPO3 backend. In the module
 :guilabel:`Backend Users` you can change the passwords of existing users,
@@ -112,9 +112,9 @@ During troubleshooting, in the :guilabel:`"Settings > Configuration Presets"`
 section of the Install Tool, under "Debug settings", the "Debug" preset can be
 change to show errors in the frontend.
 
-.. include:: /Images/AutomaticScreenshots/DebugSettings/ConfigurationPresets.rst.txt
+.. include:: /Images/ManualScreenshots/DebugSettings/ConfigurationPresets.rst.txt
 
-.. include:: /Images/AutomaticScreenshots/DebugSettings/DebugSettings.rst.txt
+.. include:: /Images/ManualScreenshots/DebugSettings/DebugSettings.rst.txt
 
 The following TypoScript setting can also be added to the root TypoScript for
 the site to show additional debug information.

diff --git a/Documentation/Administration/Upgrade/Major/PreupgradeTasks/Index.rst b/Documentation/Administration/Upgrade/Major/PreupgradeTasks/Index.rst
@@ -149,7 +149,7 @@ There are 3 different methods you can use to read the changelogs:
 #.  Read the changelog in the :ref:`Extension Scanner <t3coreapi:extension-scanner>`
     (as explained above).
 
-..  include:: /Images/AutomaticScreenshots/Upgrade/UpgradeAnalysis.rst.txt
+..  include:: /Images/ManualScreenshots/Upgrade/UpgradeAnalysis.rst.txt
 
 
 ..  _handling-deprecations:

diff --git a/Documentation/Administration/Upgrade/MigrateContent/Index.rst b/Documentation/Administration/Upgrade/MigrateContent/Index.rst
@@ -70,11 +70,11 @@ Manual export from the TYPO3 backend
       On the page tree left click on the page from where you want to start the
       export. Select :guilabel:`More options ...`:
 
-      .. include:: /Images/AutomaticScreenshots/ImportExport/ContextMenuMore.rst.txt
+      .. include:: /Images/ManualScreenshots/ImportExport/ContextMenuMore.rst.txt
 
       Then select :guilabel:`Export` from the context menu.
 
-      .. include:: /Images/AutomaticScreenshots/ImportExport/ContextMenuExport.rst.txt
+      .. include:: /Images/ManualScreenshots/ImportExport/ContextMenuExport.rst.txt
 
    2. Select the tables to be exported
 
@@ -83,15 +83,15 @@ Manual export from the TYPO3 backend
       is also possible to include static relations to tables already present
       in the target installation.
 
-      .. include:: /Images/AutomaticScreenshots/ImportExport/ExportDialog.rst.txt
+      .. include:: /Images/ManualScreenshots/ImportExport/ExportDialog.rst.txt
 
    3. Choose number of levels to be exported
 
       If you want to save all your data, including subpages,
       select 'Infinite' from the :guilabel:`Levels` select box and hit the
       :guilabel:`Update` Button at the end of the dialog.
 
-      .. include:: /Images/AutomaticScreenshots/ImportExport/ExportDialogInfiniteLevels.rst.txt
+      .. include:: /Images/ManualScreenshots/ImportExport/ExportDialogInfiniteLevels.rst.txt
 
    4. Check the included records
 
@@ -104,14 +104,14 @@ Manual export from the TYPO3 backend
       orange exclamation mark. Reasons for lost relations include records
       stored outside the page tree to be exported and excluded tables.
 
-      .. include:: /Images/AutomaticScreenshots/ImportExport/CheckExport.rst.txt
+      .. include:: /Images/ManualScreenshots/ImportExport/CheckExport.rst.txt
 
    5. Save or export the data
 
       You can save the exported data to your server or download it in the
       tab :guilabel:`File & Preset`.
 
-      .. include:: /Images/AutomaticScreenshots/ImportExport/DownloadExport.rst.txt
+      .. include:: /Images/ManualScreenshots/ImportExport/DownloadExport.rst.txt
 
 Import your data
 ================
@@ -162,7 +162,7 @@ Manual import from the TYPO3 backend
       the imported page should be as starting point for the import. If you
       want to import the data at root-level, choose the
 
-      .. include:: /Images/AutomaticScreenshots/ImportExport/UploadImport.rst.txt
+      .. include:: /Images/ManualScreenshots/ImportExport/UploadImport.rst.txt
 
    2. Preview the data do be imported
 

diff --git a/Documentation/ApiOverview/Authentication/AuthenticationService/Index.rst b/Documentation/ApiOverview/Authentication/AuthenticationService/Index.rst
@@ -47,7 +47,7 @@ view:
     Until TYPO3 V14 this module was found in :guilabel:`System > Reports`.
     See also: `Feature: #107628 - Improved backend module naming and structure <https://docs.typo3.org/permalink/changelog:feature-107628-1729026000>`_.
 
-..  include:: /Images/AutomaticScreenshots/Authentication/InstalledAuthServices.rst.txt
+..  include:: /Images/ManualScreenshots/Authentication/InstalledAuthServices.rst.txt
 
 ..  note::
 

diff --git a/Documentation/ApiOverview/Authentication/MultiFactorAuthentication/Index.rst b/Documentation/ApiOverview/Authentication/MultiFactorAuthentication/Index.rst
@@ -43,7 +43,7 @@ authentication or frontend authentication with a multi-factor step in-between.
 Managing MFA providers is currently possible via the :guilabel:`User Settings`
 module in the tab called :guilabel:`Account security`.
 
-..  include:: /Images/AutomaticScreenshots/Authentication/MfaActivate.rst.txt
+..  include:: /Images/ManualScreenshots/Authentication/MfaActivate.rst.txt
 
 The :guilabel:`Account security` tab displays the current state:
 
@@ -78,7 +78,7 @@ provider is active. It is only meant as a fallback provider, in case the
 authentication credentials for the "main" provider(s) are lost. It is encouraged
 to activate this provider, and keep the codes at a safe place.
 
-..  include:: /Images/AutomaticScreenshots/Authentication/MfaSelectProvider.rst.txt
+..  include:: /Images/ManualScreenshots/Authentication/MfaSelectProvider.rst.txt
 
 Third-party MFA providers
 -------------------------
@@ -106,7 +106,7 @@ Each inactive provider contains a :guilabel:`Setup` button which opens the
 corresponding configuration view. This view can be different depending on the
 MFA provider.
 
-..  include:: /Images/AutomaticScreenshots/Authentication/MfaQrCode.rst.txt
+..  include:: /Images/ManualScreenshots/Authentication/MfaQrCode.rst.txt
 
 Each provider contains an :guilabel:`Edit/Change` button, which allows to adjust
 the provider's settings. This view allows, for example, to set a provider as the
@@ -178,7 +178,7 @@ of all currently registered providers in the installation. This is especially
 helpful to find out the exact provider identifier, needed for some
 user TSconfig options.
 
-..  include:: /Images/AutomaticScreenshots/Authentication/MfaConfigurationModule.rst.txt
+..  include:: /Images/ManualScreenshots/Authentication/MfaConfigurationModule.rst.txt
 
 
 Configuration

diff --git a/Documentation/ApiOverview/Backend/AccessControl/AccessControlOptions/Index.rst b/Documentation/ApiOverview/Backend/AccessControl/AccessControlOptions/Index.rst
@@ -139,7 +139,7 @@ is the folder tree drawn based on *file mounts* configured for the user.
 **DB mounts** (page mounts) are set by pointing out the
 page that should be mounted for the user (at user or group-level):
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/DbMounts.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/DbMounts.rst.txt
 
 This is what the user will see:
 
@@ -167,7 +167,7 @@ upon installation.
    changed using the global configuration option
    :code:`$GLOBALS['TYPO3_CONF_VARS']['BE']['fileadminDir']`.
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/FileStorage.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/FileStorage.rst.txt
 
 
 A *File Storage* is essentially defined by a *File Driver*
@@ -176,14 +176,14 @@ and the path to which it points.
 Next we can create a *File Mount* record (on the root page),
 which refers to a File Storage:
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/CreateFilemount.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/CreateFilemount.rst.txt
 
 
 When defining a File Mount, you can point to a specific folder
 within the chosen File Storage. Finally the mount is assigned
 to a user or group:
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/AssignFilemount.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/AssignFilemount.rst.txt
 
 
 After a successful configuration, the file mount will appear to
@@ -202,7 +202,7 @@ the default behaviour. So make sure to unset these flags if users
 should see only their "private" mount points and not those from their
 groups:
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/MountFromGroups.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/MountFromGroups.rst.txt
 
 
 "Admin" users do not need mount points. As always, they have access
@@ -254,7 +254,7 @@ module:
     Until TYPO3 V14 this module was called :guilabel:`System > Permissions`.
     See also: `Feature: #107628 - Improved backend module naming and structure <https://docs.typo3.org/permalink/changelog:feature-107628-1729026000>`_.
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/AccessModule.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/AccessModule.rst.txt
 
 
 Editing permissions is described in details in chapter

diff --git a/Documentation/ApiOverview/Backend/AccessControl/MoreAboutFileMounts/Index.rst b/Documentation/ApiOverview/Backend/AccessControl/MoreAboutFileMounts/Index.rst
@@ -68,7 +68,7 @@ Paths for local driver storage
 The file storages based on the "local file system" driver have an
 option for relative or absolute paths.
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/LocalStoragePath.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/LocalStoragePath.rst.txt
 
 
 "Relative" means that the given path is relative to the :file:`fileadmin/`

diff --git a/Documentation/ApiOverview/Backend/AccessControl/OverviewOfUsers/Index.rst b/Documentation/ApiOverview/Backend/AccessControl/OverviewOfUsers/Index.rst
@@ -25,7 +25,7 @@ Just add users using the
 For example, this is the comparison of the three different editors
 provided by the Introduction Package:
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/CompareUsers.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/CompareUsers.rst.txt
 
 The same functionality is available for user groups, including a comparison
 of their inherited permissions.
@@ -36,11 +36,11 @@ Impersonating Users ("Switch to")
 We can impersonate (switch) to a user by clicking the :guilabel:`Switch to user`
 action icon:
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/SimulateUserButton.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/SimulateUserButton.rst.txt
 
 You will then be logged in as that user (note how the user name
 is prefixed with "SU" for "Simulated User"). To "switch back",
 use the "Exit" button (which replaces the usual "Logout"
 button).
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/SimulatedUser.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/SimulatedUser.rst.txt
diff --git a/Documentation/ApiOverview/Backend/AccessControl/UsersAndGroups/Index.rst b/Documentation/ApiOverview/Backend/AccessControl/UsersAndGroups/Index.rst
@@ -18,7 +18,7 @@ Each user of the backend must be represented with a single record in
 the table "be\_users". This record contains the username and password,
 other meta data and some permissions settings.
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/BackendUser.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/BackendUser.rst.txt
 
 
 The above screenshot shows a part of the editing form for the backend
@@ -45,7 +45,7 @@ When a user is a member of many groups (including sub-groups) then the
 permission settings are added together so that the more groups a user
 is a member of, the more access is granted to him.
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/BackendGroup.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/BackendGroup.rst.txt
 
 
 This screenshot shows just an extract of the group editing form.
@@ -75,7 +75,7 @@ will most likely grant them access to more than they need.
 
 Admin users are differentiated with an orange icon.
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/BackendUserAdmin.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/BackendUserAdmin.rst.txt
 
 .. note::
 
@@ -102,7 +102,7 @@ system. However backend users and groups are configured to exist
 *only* in the root of the page tree where *only* admin users have
 access:
 
-.. include:: /Images/AutomaticScreenshots/AccessControl/BackendUserList.rst.txt
+.. include:: /Images/ManualScreenshots/AccessControl/BackendUserList.rst.txt
 
 
 Records located in the page tree root are identified by having their

diff --git a/Documentation/ApiOverview/Backend/BackendLayout.rst b/Documentation/ApiOverview/Backend/BackendLayout.rst
@@ -34,7 +34,7 @@ layouts are available if an
 backend layouts have been
 :ref:`defined as records or page TSconfig <be-layout-definition>`.
 
-.. include:: /Images/AutomaticScreenshots/BackendLayouts/PagePropertiesAppearance.rst.txt
+.. include:: /Images/ManualScreenshots/BackendLayouts/PagePropertiesAppearance.rst.txt
 
 ..  versionchanged:: 14.0
     The main module `web` has been renamed to `content`.
@@ -45,7 +45,7 @@ The :guilabel:`Content > Status` module gives an overview of the backend layouts
 inherited from a parent page at
 :guilabel:`Content > Status > Pagetree overview > Type: Layouts`:
 
-.. include:: /Images/AutomaticScreenshots/BackendLayouts/PageTreeLayoutOverview.rst.txt
+.. include:: /Images/ManualScreenshots/BackendLayouts/PageTreeLayoutOverview.rst.txt
 
 .. index::
    Backend layout; Record

diff --git a/Documentation/ApiOverview/Backend/BackendModules/BackendGUI.rst b/Documentation/ApiOverview/Backend/BackendModules/BackendGUI.rst
@@ -12,7 +12,7 @@ system extension and extended by many other system extensions.
 
 It is divided into the following main areas:
 
-.. include:: /Images/AutomaticScreenshots/BackendModules/BackendModulesAreas.rst.txt
+.. include:: /Images/ManualScreenshots/BackendModules/BackendModulesAreas.rst.txt
 
 Top bar
   The top bar is always present. It is itself divided into two
@@ -66,4 +66,4 @@ Contextual menus
   mechanisms vary: the page tree behaves differently than the
   rest of the backend.
 
-  .. include:: /Images/AutomaticScreenshots/BackendModules/BackendModulesContextualMenu.rst.txt
+  .. include:: /Images/ManualScreenshots/BackendModules/BackendModulesContextualMenu.rst.txt
diff --git a/Documentation/ApiOverview/Backend/Clipboard.rst b/Documentation/ApiOverview/Backend/Clipboard.rst
@@ -23,14 +23,14 @@ In this simple piece of code we instantiate a clipboard object and make it
 load its content. We then dump this content into the BE module's debug
 window, with the following result:
 
-.. include:: /Images/AutomaticScreenshots/Examples/Clipboard/ClipboardDump.rst.txt
+.. include:: /Images/ManualScreenshots/Examples/Clipboard/ClipboardDump.rst.txt
 
 This tells us what objects are registered on the default tab ("normal")
 (a content element with id 216 in "copy" mode) and the numeric tabs (which can
 each contain more than one element). It also tells us that the current
 tab is number 2. We can compare with the BE view of the clipboard:
 
-.. include:: /Images/AutomaticScreenshots/Examples/Clipboard/ClipboardContent.rst.txt
+.. include:: /Images/ManualScreenshots/Examples/Clipboard/ClipboardContent.rst.txt
 
 which indeed contains two files.
 
@@ -47,4 +47,4 @@ In the "examples" extension, this data is passed to a BE module view
 for display, which is really just information:
 
 
-.. include:: /Images/AutomaticScreenshots/Examples/Clipboard/ClipboardItems.rst.txt
+.. include:: /Images/ManualScreenshots/Examples/Clipboard/ClipboardItems.rst.txt
diff --git a/Documentation/ApiOverview/Backend/ContextualMenu.rst b/Documentation/ApiOverview/Backend/ContextualMenu.rst
@@ -14,7 +14,7 @@ Contextual menus exist in many places in the TYPO3 backend. Just try your
 luck clicking on any **icon** that you see. Chances are good that a contextual
 menu will appear, offering useful functions to execute.
 
-.. include:: /Images/AutomaticScreenshots/Examples/ContextualMenuExtended/ContextMenuTtContent.rst.txt
+.. include:: /Images/ManualScreenshots/Examples/ContextualMenuExtended/ContextMenuTtContent.rst.txt
 
 .. _csm-implementation:
 
@@ -270,7 +270,7 @@ Tutorial: How to add a custom context menu item
 Follow these steps to add a custom menu item for pages records. You will add a
 "Hello world" item which will show an info after clicking.
 
-.. include:: /Images/AutomaticScreenshots/Examples/ContextualMenuExtended/ContextMenuHelloWorld.rst.txt
+.. include:: /Images/ManualScreenshots/Examples/ContextualMenuExtended/ContextMenuHelloWorld.rst.txt
 
 Step 1: Implementation of the item provider class
 -------------------------------------------------