Learn / Guide

How to Customize Rainmeter Skins and Save Your Layout

Move widgets, edit supported settings and back up both layouts and skin files without confusing the two.

Editorial: DeskSpruce Published

Use Rainmeter's Manage window for position and window behavior. Use the skin creator's settings or configuration files for its appearance. Save a layout before moving several widgets, and back up the skin folder before editing its files: a layout does not contain those files.

Evidence: this is a documentation-based guide, not an installation test. The controls below are documented by Rainmeter; individual skins may expose different settings.

Start with a reversible backup

  1. Open Rainmeter from its notification-area icon and select the Layouts tab.
  2. Give your current layout a new name and save it. Do not select an existing name unless you intend to replace that layout.
  3. Copy the root folder of the skin you will edit to a backup location outside the active Skins folder. Keep its supporting files and @Resources folder together.

A layout records active and inactive skins, positions and Rainmeter settings. It does not back up a skin's .ini, .inc, images or scripts. Copy those separately before changing them.

Move a widget and keep it in place

In Manage → Skins, select the loaded configuration's .ini file. Enable Draggable to move it with the mouse, or adjust its Coordinates for a precise position. Save position retains its position; Keep on screen and Snap to edges control how it sits within the display.

When you are satisfied, disable Draggable if you keep moving the widget by accident. If Click through is enabled, use Manage rather than trying to interact with the widget itself. Check Display monitor when using multiple screens.

Change color, font or size only where supported

First read the creator's instructions and look for a supplied settings skin or custom skin action. There is no universal Rainmeter scale slider that every skin supports. A suite may calculate size from its own variables; editing one font size does not necessarily resize its backgrounds, icons and click targets.

  1. Select the intended configuration in Manage and choose Edit.
  2. Find the documented variable or option. It may live in an included .inc file rather than in the selected .ini.
  3. Change one value, save the file, then choose Refresh for that skin.
  4. If the result is wrong, restore the saved value or your file backup and refresh again.

For example, a string meter can use FontColor=255,255,255,255 for opaque white. This is a Rainmeter option example, not an instruction to paste it into every skin: a shared style or variable may control the actual value. Rainmeter supports decimal RGBA and hexadecimal color notation. Do not edit launch commands or power actions when you only mean to change appearance.

Understand variants before loading another file

Multiple .ini files in one configuration folder are variants. Only one variant in that folder can run at a time. A 12-hour and a 24-hour variant may therefore replace one another rather than display side by side. Separate configuration folders can run independently.

Save the finished layout and restore it later

Return to Layouts and save under a distinct name. Include current wallpaper is optional; loading a layout with a saved wallpaper changes the desktop wallpaper as well. To restore a layout, select it in Saved layouts and choose Load. Loading changes the current Rainmeter state; Rainmeter automatically saves the previous state as @Backup.

If a file edit broke the skin, loading an old layout alone will not repair it. Restore the skin files too. Before updating a customized package, preserve its files outside the active library so the update cannot overwrite your only copy.

If your changes do not appear

Check that you edited the configuration actually loaded in Manage, saved the correct file and refreshed the skin. A setting may be supplied by an include or calculated from a variable. For a missing widget, use the not-showing checklist. For a new package, follow the installation guide instead.

Primary references