Troubleshooting and workflow notes

Step 1

Keep a backup outside the browser

2D Tiler is designed to run locally in the browser, which is convenient for fast editing. For long-running projects, export native .2dp backups so your work is also stored outside browser-managed data.

1. Save normally while editing.
2. Export a .2dp backup at milestones.
3. Keep backup files in the same versioned project folder as your game assets.

Step 2

Keep linked resources together

Several external formats use linked image resources or sidecar files. When importing or exporting a bundle, keep the map, tileset, image, manifest, and metadata files together until the target engine has accepted them.

• Phaser bundles use linked tileset images.
• Unity bundles can include prefab, Tile assets, manifests, texture images, and .meta files.
• Defold and Tiled workflows can reference external tileset image resources.

Step 3

Check tileset spacing before import

The current core tileset model works best with dense grid-aligned source art. If an external tileset uses margins or spacing, normalize the source image before relying on grid coordinate round trips.

• Use a consistent tile size across map and tileset.
• Avoid hidden margins between tiles when possible.
• Review imported tile placement before making broad map edits.

Step 4

Review provider setup for AI generation

AI image generation depends on the selected provider. If generation fails, check the API key, provider quota, model availability, prompt requirements, and whether the selected model supports reference-image input.