Global Settings Panel
The Global Settings panel is accessed by going to the Plugin Dashboard, then the Top Bar, then clicking the Settings button.
In the Global Settings panel you can configure plugin-wide defaults that affect all modules, unless overridden inside a module.

Save Global Settings (Button)
After making changes in the Global Settings panel, click the Save Global Settings button to save your changes. The button is available in the bottom right corner of any tab 1.

General Tab
In the General tab handle permissions & language, JS library loading, and alignment & snapping tools for the Module Editor.

Permission & Language Section
In the Permissions & Language section configure editing permissions, the editing language, and whether you would like to share usage analytics.

Editing Permission (Dropdown)
Set the level of WordPress permission required to edit modules.

Options:
- Admin: Only users with “Admin” permission can edit modules.
- Editor, Admin: Users with “Editor” or “Admin” permission can edit modules.
- Author, Editor, Admin: Users with “Author”, “Editor” or “Admin” permission can edit modules.
Editing Language (Dropdown)
Set the language used in the Slider Revolution interface.

Options:
- Default: Uses whatever language is set as the WordPress “Site Language”.
- German: Set the interface to use German language.
- English: Set the interface to use English language.
- French: Set the interface to use French language.
- Chinese: Set the interface to use Chinese language.
Share Slider Revolution Usage Analytics (Toggle)
Opt in to sharing usage analytics to assist us in continually improving Slider Revolution.

Options:
- On: Share usage analytics.
- Off: Do not share usage analytics.
Slider Revolution JS Libraries Section
In the Slider Revolution JS Libraries section control where and how JavaScript libraries are loaded.

Load JS Libraries Globally (Toggle)
Set whether to load Slider Revolution JS libraries everywhere on the site, or only on specified pages.

Options:
- On: SR JS libraries load everywhere on the site.
- Off: Shows the Pages to Load SR JS Libraries setting. SR JS libraries only load where specified in that setting.
Pages to Load SR JS Libraries (Multi-select)
When not loading SR JS libraries globally, specify where to load them. By default loads in All Pages With SR.

To add other loading locations click to expand the setting, enter a comma separated list of page/post IDs in the Add Page Id field 1 then click the + button 2.

Check or uncheck the box to the left of each location as required to load JS libraries where you wish.

Editor Behavior Section
In the Editor Behavior section configure assistants for alignment and snapping in the Module Editor.

Enable Align Guide Lines (Toggle)
Set whether to show alignment guides on the Stage of the Module Editor when dragging a layer and its edges approach alignment targets.

Alignment targets include the Stage center or middle, and the edges/center/middle of other layers.
Options:
- On: Show align guide lines.
- Off: Do not show align guide lines
Align Threshold (Number, range)
Set how close a layer’s edge must be to an alignment target before an align guide line appears.

Options:
- 5: Minimum. Layer edge must be 5 pixels or less away from an alignment target before a guide line appears.
- 50: Maximum. Layer edge must be 50 pixels or less away from an alignment target before a guide line appears.
Allow Align Position Snap (Toggle)
Set whether layers should snap into position when their edge nears an alignment target.

Options:
- On: When the layer’s edge nears an alignment target, the layer position snaps such that the edge aligns with the target.
- Off: When the layer’s edge nears an alignment target its position does not change.
Snap Threshold (Number, range)
If Allow Align Position Snap is toggled On, set how close a layer’s edge must be to an alignment target before position snapping occurs.

Options:
- 5: Minimum. Layer edge must be 5 pixels or less away from an alignment target before position snapping occurs.
- 50: Maximum. Layer edge must be 50 pixels or less away from an alignment target before position snapping occurs.
Breakpoints Tab
In the Breakpoints tab, set the widths at which module layouts should switch to different device sizes.

Wide Screen Breakpoint (Number, pixels, range)
Set the viewport width at which the Wide Screen layout will be activated.

Options:
- 1240px: Minimum. The smallest width at which the Wide Screen layout can be activated.
- 2800px: Maximum. The largest width at which the Wide Screen layout can be activated.
Desktop Breakpoint (Number, pixels, range)
Set the viewport width at which the Desktop layout will be activated.

Options:
- 960px: Minimum. The smallest width at which the Desktop layout can be activated.
- 1640px: Maximum. The largest width at which the Desktop layout can be activated.
Notebook Breakpoint (Number, pixels, range)
Set the viewport width at which the Notebook layout will be activated.

Options:
- 778px: Minimum. The smallest width at which the Notebook layout can be activated.
- 1240px: Maximum. The largest width at which the Notebook layout can be activated.
Tablet Breakpoint (Number, pixels, range)
Set the viewport width at which the Tablet layout will be activated.

Options:
- 640px: Minimum. The smallest width at which the Tablet layout can be activated.
- 1240px: Maximum. The largest width at which the Tablet layout can be activated.
Mobile Breakpoint (Number, pixels, range)
Set the viewport width at which the Mobile layout will be activated.

Options:
- 0px: Minimum. The smallest width at which the Mobile layout can be activated.
- 640px: Maximum. The largest width at which the Mobile layout can be activated.
Breakpoints Include Scrollbar Width (Toggle)
Set whether to include the width of the scrollbar in calculating when breakpoints should trigger layout change.

Options:
- On: Layout changes when the full window width (viewport + scrollbar) equals the breakpoint.
- Off: Layout changes when the viewport width equals the breakpoint.
Fonts Tab
In the Fonts tab configure Google Font loading and caching, Font Awesome loading, and custom font addition.

Font Loading and Caching Section
Under Font Loading and Caching set where you want to load Google fonts from, manage font caching, and optionally toggle Font Awesome inclusion and Google Font preconnects.

Google Fonts Download (Dropdown)
Set how you would like to load and cache Google Font files.

Note that if you choose Cache Fonts Locally you will be prompted to initiating precaching to ensure fonts will be available in the front end.
Options:
- Load from Google: Load font files from Google, and allow Google to handle caching.
- Cache Fonts Locally: Load font files from Google, but cache files locally on your site’s server.
- Disable, Load on Your Own: Don’t load Google font files through Slider Revolution at all. Handle font loading via your own preferred method.
Clear and Recache Fonts (Button)
Deletes any existing Google font files stored in cache, and fetches fresh copies of fonts into cache.

Only fonts used in modules will be fetched.
Use this button if you have stopped using one or more fonts and want to remove them from cache.
Update Font Cache (Button)
Updates the font cache to add any fonts used in modules that are not already cached.

Be sure to use this button any time a previously unused font is used in a module design.
Disable SR Font Awesome Library (Toggle)
Set whether to disable Slider Revolution’s Font Awesome library. If you are already loading Font Awesome from a different source you may wish to use this setting to prevent double loading.

Options:
- On: Don’t use the SR Font Awesome library.
- Off: Use the SR Font Awesome library.
Disable Google Font Preconnects (Toggle)
Set whether to use Google Font’s preconnect functionality.

Options:
- On: Don’t use Google Font preconnect.
- Off: Use Google Font preconnect.
Google Fonts Loading URL Section
Custom Font URL (Text)
Set an alternative Google Fonts loading URL.

Custom Fonts Section
In the Custom Fonts section add custom fonts by clicking the Add Custom Font button then filling in the custom font fields.

Add Custom Font (Button)
Click the Add Custom Font button 1 to add a new custom font configuration form 2, in which you can specify the details of the custom font you wish to use.

Custom Font Configuration (Form)
For each custom font added, there are four settings that should be configured: Name 1, CSS URL 2, Weight 3, Load In 4.

Name (Text)
Set the name of the custom font, for example “Barlow”.

The name of the custom font must match the name in the CSS file provided in the CSS URL setting.
This is the name you’ll later select in the Module Editor to apply the font to a Text layer, via Design mode -> Style tab -> Text section -> Font.
CSS URL (Text)
Set the URL for the CSS file that loads the custom font using @font-face code.

For example, the Barlow font can be loaded via the CSS URL https://fonts.bunny.net/css?family=barlow
Note that the provided URL must be for a CSS file, and not for a font file directly.
Both locally hosted font CSS files, or files from a third party CDNs such as Adobe Fonts, Bunny Fonts and so on are allowed.
For information on how to prepare @font-face CSS visit MDN Web docs.
Weight (Text)
Set the weights of the custom font as a comma separated list.

For example, the normal weight, normal & italic, and bold weight of the Barlow font can be loaded with 400,400i,700.
Load In (Dropdown)
Set whether to load the custom font in the Module Editor and/or in the live front end.

Options:
- Editor & Live: Load the custom font in the module editor and live front end.
- Live: Load the custom font in the live front end only. Use this option if you want to use Slider Revolution’s font loader for purposes other than module editing.
- Editor: Load the custom font in the module editor only. Use this option when you’re loading custom fonts via an alternative method, but still want to see those fonts in the module editor.
Delete (Button)
Click the delete button to remove the custom font configuration form, and the associate custom font.

Optimization Tab
In the Optimization tab configure module content loading methods, mobile DPR handling, and image optimization.

Module Optimization & Loading Section
In the Module Optimization & Loading section configure the data and feed loading method you would like to use, and optionally force 1xDPR on mobile devices.

SR7 Data Load Method (Dropdown)
Set the loading method for module assets such as images and videos.

Note that regardless of data load method, a module’s entire HTML content is always present and available for SEO purposes.
Options:
- Smart Loading: Load visible module assets, and progressively load assets from slides about to be navigated to, or modules about to scroll into view. Balances initial load speed with smooth page & module navigation.
- Preloading: Load all module assets before displaying the module. Prioritizes smooth page & module navigation over initial load speed.
- On Demand Loading: Load module assets only when required. Prioritizes initial load speed over smooth page & module navigation.
SR7 Feeds Load Method (Dropdown)
Set the loading method for content drawn from feeds, such as social media posts or image galleries.

Options:
- Preloading: Fetch all feed content before displaying the module. May have longer initial load time, but ensures no delay when navigating the module.
- On Demand Loading: Fetch feed content only when about to be displayed. Faster initial load time, but may cause slight delay when navigating the module.
Force 1xDPR on mobile (Toggle)
Set whether to force mobile devices with high DPR (device pixel ratio) screens to treat canvas animated content as 1xDPR.

Activating this setting prevents canvas elements such as background images from being internally scaled up 2x or 3x, locking them in at their original resolution.
May cause images to appear more blurry, but can reduce load on the GPU/CPU.
Options:
- On: Force 1xDPR content rendering.
- Off: Allow high DPR devices to scale content to 2xDPR or 3xDPR.
Image Optimization Section
In the Image Optimization section configure automatic image optimization settings.

Note that at least one of the settings On Save or On The Fly need to be toggled on, otherwise image optimization processes will not be run in the Module Editor.
It can instead be run per slide manually via the Module Section of the Plugin Dashboard, by navigating into the Slide items of a module, expanding the Item Menu for a slide, and clicking the Optimize button.
On Save (Toggle)
Set whether to run image optimizations when you save a module.

Options:
- On: Images will be optimized when you save a module.
- Off: Save a module will not trigger image optimization. Optimization may still be triggered if On The Fly is toggled to On.
On The Fly (Toggle)
Set whether to run image optimizations in the background as you work on a module.

Options:
- On: Images will be optimized as you work, with no need for manual action.
- Off: Images will not be optimized in the background. Optimization may still be triggered if On Save is toggled to On.
Image Format (Dropdown)
Set whether optimized images should be save in WebP format, or retain their original format.

Options:
- WebP: All images will be converted to WebP format.
- Original: Images will retain their original format.
Max Img. Scale Multiplier (Number, range)
Set how much larger an image can be than the size at which it is set to appear via the Module Editor.

Options:
- 1: Minimum. The image is optimized to be the same dimensions it’s configured to have via the Module Editor.
- 2: Maximum. The image is optimized at up to twice the dimensions it’s configured to have via the Module Editor.
Quality (Number, range)
Set the quality at which optimized images should be created. Lower numbers create images with decreased quality but faster load speed. Higher numbers create images with better quality but slower load speed.

It is recommended to stick with the default of 85 for most cases.
Options:
- 50: Minimum. The lowest quality but fastest loading images.
- 100: Maximum. The highest quality but slowest loading images.
Max Width (Number, pixels, range)
Set the maximum width for optimized images. Any images originally greater in width than this amount will be shrunk.

Options:
- 200px: Minimum. The narrowest possible maximum width for optimized images.
- 2048px: Maximum. The widest possible maximum width for optimized images.
Max Height (Number, pixels, range)
Set the maximum height for optimized images. Any images originally greater in height than this amount will be shrunk.

Options:
- 200px: Minimum. The shortest possible maximum height for optimized images.
- 2048px: Maximum. The tallest possible maximum height for optimized images.
System Tab
In the System tab configure cookie consent management, content caching, and database health & repair.

Privacy & GDPR Settings Section
In the Privacy & GDPR Settings section toggle YouTube No-Cookie mode, and choose a cookie consent plugin to integrate with.

YouTube No-Cookie Mode (Toggle)
Set whether to load any YouTube videos via “youtube-nocookie.com” instead of the standard “youtube.com” domain. Enabling this setting prevents YouTube from setting a cookie unless the video is interacted with by the visitor, e.g. playing the video.

Note that for GDPR compliance cookie consent will still be required if the visitor decides to play the video, it just won’t automatically be required the moment the page loads, as is the case if embedding via “youtube.com”.
Options:
- On: Embedded YouTube videos are loaded via “youtube-nocookie.com”.
- Off: Embedded YouTube videos are loaded via “youtube.com”.
Consent Management Plugin (Dropdown)
Set how YouTube and Vimeo videos are loaded, depending on the active consent management plugin.

If set to None, videos are always allowed to play without asking for consent to set cookies.
If a consent management plugin is selected, that plugin will request cookie consent in the browser.
If consent is given within 15 seconds, the video is then loaded. If no consent is given, the video stays blocked until the next page load.
Options:
- None:
- Borlabs Cookie:
- Complianz:
- Cookiebot CMP:
- Cookie Notice:
- Cookie Yes:
- GDPR Cookie Comp.:
- Real Cookie Banner:
Category (Dropdown)
Set the category of cookie for which consent should be requested.

Options:
- Functional
- Marketing
- Preferences
- Statistics
Content Caching Section
In the Content Caching section toggle internal caching, and handle cache clearing.

Use Internal Caching (Toggle)
Set whether or not to use Slider Revolution’s built-in caching system.

Options:
- On: Save resources into the built-in cache.
- Off: Do not save resources into the built-in cache.
Clear Internal Cache (Button)
Click to clear any stored information in the Slider Revolution built-in cache.

Database Health & Repair Section
In the Database Health & Repair section handle unmigrated module deletion, database scanning and missing table repair.

Delete Unmigrated Modules (Button)
If you have modules created in Slider Revolution 6 that have not been migrated to version 7, and you no longer need them, click this button to delete those modules.

Scan Database Health (Button)
Click to check if the database is using the required, up to date structure.

Fix Missing SR7 Tables (Button)
If any database tables required by Slider Revolution 7 are missing, click this button to add them.

