Since launching Simply Customize It I've switched both my reMarkable devices to the beta track to stay ahead of any changes. The latest 3.18 update introduced some unexpected differences like extra templates on my reMarkable 2 (3.18.0.67) and what I thought were missing template images on my Paper Pro (3.18.0.70).

After digging into what changed, I realized reMarkable had altered its template structure. In this post, I’ll break down the key changes in reMarkable’s update and how Simply Customize It has been updated to ensure everything keeps working smoothly.

Quick Note

I own both the reMarkable 2 and the Paper Pro. While I assume the reMarkable 1 follows the same changes as the 2, I’d love to hear from you if you’ve noticed differences! Feel free to comment below or email me at mail@simplykyra.com.

TLDR

This update ensures seamless template syncing with reMarkable version 3.18. It adds support for the new .template files, improves how templates are detected to reduce duplicates, and introduces the ability to duplicate a device.

reMarkable Changes in Version 3.18

Interface Changes

Both devices changed where the layer button is and, once you go into templates, where the categories are stored.

File Structures and Template Changes

In version 3.18.0.67, using my reMarkable 2, I noticed duplicate JSON entries for some templates. These templates now included a new optional field in the JSON file called supportedScreens that contained either rm2 or rmPP. The rmPP version also altered the filename to include variant. Here's the example for Week Planner 1:

        {
            "name": "Week planner 1",
            "filename": "P Week",
            "supportedScreens": [
                "rm2"
            ],
            "iconCode": "\ue9dc",
            "categories": [
                "Planners"
            ]
        },
        {
            "name": "Week planner 1",
            "filename": "P Week variant",
            "supportedScreens": [
                "rmPP"
            ],
            "iconCode": "\ue9dc",
            "categories": [
                "Planners"
            ]
        },

However, in version 3.18.0.70 (seen in both devices), the duplicate entries were removed with the supportedScreens field combining the two values into a single entry and no mention of variant:

    {
      "name": "Week planner 1",
      "filename": "P Week",
      "supportedScreens": ["rm2", "rmPP"],
      "iconCode": "\ue9dc",
      "categories": ["Planners"]
    },

New .template Files

Some templates now use a .template file instead of an SVG or PNG image. For example here's the contents of the .template file for the Grid Large template:

{
    "name": "Grid large",
    "author": "reMarkable",
    "templateVersion": "0.0.1",
    "formatVersion": 1,
    "categories": ["All"],
    "orientation": "portrait",
    "constants": [
        { "gridSize": 104 },
        { "magicOffset": -78 },
        { "xpos": "templateWidth / 2 - templateHeight / 2 + magicOffset" }
    ],
    "items": [
        {
            "id": "hlines",
            "type": "group",
            "boundingBox": { "x": 0, "y": 0, "width": "templateWidth", "height": "gridSize" },
            "repeat": { "rows": "infinite", "columns": "infinite" },
            "children": [
                {
                    "id": "hline",
                    "type": "path",
                    "data": [ "M", 0, 0, "L", "parentWidth", 0 ]
                }
            ]
        }, {
            "id": "vlines",
            "type": "group",
            "boundingBox": { "x": "xpos", "y": 0, "width": "gridSize", "height": "templateHeight" },
            "repeat": { "rows": "infinite", "columns": "infinite" },
            "children": [
                {
                    "id": "vline",
                    "type": "path",
                    "data": [ "M", 0, 0, "L", 0, "parentHeight" ]
                }
            ]
        }
    ]
}

Do Only PNG Custom Templates Still Work?

Both reMarkable devices still let templates work with just a PNG or SVG image file, but if a .template file is present, it takes priority over both.

What’s New in Version 1.0.8

To ensure compatibility with reMarkable 3.18, Simply Customize It now supports:

Updated JSON Handling

• The app now reads in the supportedScreens field and only imports templates meant for your device thus preventing duplicates in a single import.
• When syncing or uploading templates the supportedScreens field is not saved which keeps the file structure clean.

Improved Template Import Logic

Previously, a template was considered new if there was no current template that matched its:

• name
• landscape/portrait orientation
• filename

This caused issues when the filename changed (with variant added in 3.18.0.67). Now instead of filenames the app relies on icon codes to reduce unnecessary duplicate templates while still ensuring accurate imports.

Support for .template Files

• The app now saves .template files alongside PNG and SVG images.
• You can view (but not edit) the .template files within the app.
• When browsing templates the app will display the SVG image first, followed by the PNG image. If neither is available, a default image will indicate that a .template file is set.

New Duplicate This Device Button

While switching between devices, I realized it would be helpful to copy a device’s connection details without keeping its templates or screens. Now, you can:

• Duplicate a device with one tap
• Use it as a backup or a starting point for another device

Are PNG Images Still Supported?

Yes! PNG-only custom templates still work. However, if a .template file is available, the reMarkable will prefer that over both SVG and PNG images.

To recap:

1. If a .template file exists, reMarkable uses that.
2. If no .template file, it defaults to the SVG.
3. If no SVG, it falls back to the PNG.

And that's the app update!

I hope this makes the transition to reMarkable 3.18 smoother for you! If you have any questions, feedback, or feature requests, feel free to:

• Leave a comment below
• Email me at mail@simplykyra.com

Thanks for reading and happy customizing!