Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

RPG Maker MZ expects image assets in PNG format, but it does not impose one universal canvas size. The correct dimensions depend on the asset category: faces, battlebacks, and title screens have documented sizes; pictures, parallaxes, and several enemy graphics can use flexible dimensions; character sheets must follow a precise grid. MZ also changes how a character is positioned or shaded based on filename markers such as ! and $. Use the project’s tile-size setting and the rules for the specific image type before resizing artwork.

What image format does RPG Maker MZ use?

The RPG Maker MZ Help documentation states: “All images must be in the PNG format.” That rule applies across the image categories covered by the asset standards documentation, including face graphics, character sheets, pictures, parallaxes, battlebacks, tilesets, title-screen images, and enemy graphics.

PNG is important for more than file-name compatibility. It can retain an alpha channel, so transparent pixels in a sprite, picture, or other asset remain transparent when MZ renders the image. If an image looks translucent in-game, do not assume the PNG itself is defective: MZ can also apply a bush effect to map characters, and that effect is controlled partly by the character filename.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Save the finished asset as a real PNG rather than merely renaming a JPEG or another format. A renamed file does not acquire PNG encoding or the transparency information MZ expects.

Which RPG Maker MZ images have fixed dimensions?

Only some categories have a prescribed canvas or cell size. The following values come from the MZ asset standards documentation.

Asset category Documented size or layout How to apply it
Battlebacks 1000 × 740 pixels Prepare the battleback at this canvas size when following the documented standard.
Face graphics 144 × 144 pixels per face; 2 rows by 4 columns Use a sheet containing eight equal face cells. The resulting sheet is 576 × 288 pixels when all eight cells are present.
Title-screen images 816 × 624 pixels Use this canvas for the documented title-screen image size.

The face-sheet total of 576 × 288 pixels is a direct calculation from eight 144-pixel cells arranged as four columns and two rows. If you use fewer faces, keep the same cell geometry and leave the remaining positions handled according to the way your project imports and selects faces.

Battlebacks

Battlebacks are documented at 1000 × 740 pixels. Keep the artwork inside that frame so the scene composition, horizon, and foreground elements land where you expect. A different canvas can still be a valid PNG, but it no longer follows the documented battleback dimension and may require you to check how the engine displays or crops it.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Face sheets

Each face occupies a 144 × 144-pixel square. The sheet is read as two rows and four columns, not as one long strip. Align every portrait to its cell boundaries; a face that crosses a boundary can be selected with part of a neighboring portrait.

Title screens

The documented title-screen image size is 816 × 624 pixels. Design the important logo and text away from edges that may be visually crowded by menu elements, while preserving the full canvas dimensions.

Which image types can use any size?

The MZ manual allows flexible dimensions for front-view enemy images, pictures, parallaxes, and side-view enemy images. “Any size” means the file is not tied to a single prescribed width and height in the asset standards; it does not mean every size will look equally sharp or fit every event and screen.

  • Pictures: choose dimensions that match the intended on-screen display and scaling. A large source can be reduced in-game, while a small source enlarged on screen can look soft.
  • Parallaxes: size the image for the map area and scroll behavior you intend to create. Check how the image loops or is positioned in the map before committing to a very wide canvas.
  • Front-view and side-view enemy images: the manual does not prescribe one canvas size. Frame the enemy so its visible body and attack area remain inside the region used by your battle presentation.

The manual also warns that images with odd horizontal widths may appear blurred and recommends even widths for the categories where that caveat is given. If an otherwise clean image looks soft, inspect its pixel width first and test an even-width version before changing the artwork or sharpening filters.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How RPG Maker MZ reads character sprite sheets

Character sheets are not free-form illustrations. MZ parses them as a grid containing four directions and three animation patterns. A normal character cell is 48 × 48 pixels in the standard described by the asset documentation, but MZ can use a different cell size when the sheet grid is built correctly.

The engine derives a character cell from the full sheet: cell width equals one-twelfth of the sheet width, and cell height equals one-eighth of the sheet height. That means a sheet is interpreted as 12 columns by 8 rows of cells. Those cells represent four directional rows of three animation patterns for each character slot, with a standard multi-character sheet holding eight characters.

Standard multi-character sheets

A normal sheet can hold eight characters. Because the engine divides the sheet into twelve columns and eight rows, the full image must have dimensions divisible by 12 horizontally and by 8 vertically. With the standard 48 × 48 cell, the resulting sheet is 576 × 384 pixels. The key requirement is consistent geometry: every slot must use the same cell size and the same directional and animation order.

Rank #3
The SNES Pixel Book
  • Spot-varnished 3mm protective board slipcase
  • Spot-varnished cover
  • Sewn binding
  • Shrink-wrapped

Single-character sheets and the $ marker

Put a dollar sign at the start of the filename to mark a single-character sheet. The $ tells MZ not to treat the image as an eight-character sheet. Without that marker, a one-character image may be divided as though it contained multiple characters, producing an apparently tiny or misaligned sprite.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The single-character image still uses the directional and animation grid expected by MZ; the marker changes how the overall sheet is interpreted, not the need for three patterns and four directions.

The ! marker, vertical offset, and bush behavior

By default, MZ displays a map character 6 pixels above its tile. A leading exclamation mark in the filename prevents that offset. The same marker also prevents bush elements from making the image appear half-transparent.

This is an engine behavior, not a transparent-pixel instruction. If a character is vertically shifted or seems translucent while standing in a bush, first check the filename. A single-character sheet that also needs the offset and bush behavior disabled uses both markers: !$ at the start of the filename.

The official RPG Maker Web explanation summarizes the markers as “$ is for single characters” and “! is for characters without the offset.” Treat these characters as functional metadata, not decorative punctuation.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How tile size changes the dimensions you should draw

Do not assume every MZ project uses 48-pixel tiles. The MZ 1.5.0 announcement lists selectable tile sizes of 16, 24, 32, and 48 pixels. The 48 × 48 tile is the standard described in the asset standards documentation, but a project configured for another value changes the scale at which tiles and map artwork are interpreted.

Before creating or resizing a tileset, open the project’s map or system settings and confirm the selected tile size. Use that setting as the basis for tile artwork and map composition. A tileset built around 48-pixel cells can be technically valid PNG artwork yet appear at the wrong scale in a project configured for 32-pixel tiles.

The tile-size list is specifically documented for the MZ 1.5.0 release announcement. If you are working with a later update or a project migrated from another version, verify the setting in that project rather than assuming the announcement describes every later change.

PNG transparency versus MZ’s apparent transparency

There are two different causes of a character looking transparent:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  1. Alpha transparency in the PNG: the artwork contains partially transparent or fully transparent pixels. This is part of the image data.
  2. The bush effect: MZ changes the appearance of a map character when it is on a bush tile. A leading ! prevents this bush-related half-transparency.

These causes can coexist. A sprite may contain semitransparent antialiasing around its outline and also receive the bush effect in-game. Inspect the source image’s alpha channel in an image editor, then test the same file on and off a bush tile. If the change occurs only on the bush tile, check whether the filename needs the ! marker before altering the artwork.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

A reliable workflow for preparing an MZ image

  1. Identify the asset category. Decide whether the file is a face, battleback, title image, character sheet, tileset, picture, parallax, or enemy graphic. Do not apply a face or character-sheet rule to a picture.
  2. Confirm the project version and settings. Name the target as RPG Maker MZ and check the project’s selected tile size, especially if the project is not using the standard 48-pixel setting.
  3. Set the canvas or grid. Use 1000 × 740 for a documented battleback, 816 × 624 for a documented title-screen image, and 144-pixel face cells arranged in four columns by two rows. For a character sheet, make the width divisible by 12 and height divisible by 8, then verify the resulting cell size.
  4. Build consistent cells. Keep every character cell the same width and height. Place the four directions and three animation patterns in the expected order, and reserve the correct number of character slots for a standard or single-character sheet.
  5. Preserve alpha where needed. Export as PNG with the intended transparent pixels. Check that the export process did not flatten the image onto a solid background.
  6. Check the filename markers. Add $ for a single-character sheet. Add ! when the character must not receive the 6-pixel offset or bush half-transparency. Combine them as !$ when both conditions apply.
  7. Check horizontal width. For flexible-size images, use an even pixel width where the manual’s blur warning applies. This can eliminate softness caused by an odd width.
  8. Test in the actual scene. View the image in the map, battle, title, or event context where it will be used. Confirm scale, cropping, alignment, animation, and transparency rather than relying only on an image editor preview.

Why a character sheet displays incorrectly

The sprite is tiny, duplicated, or cut into pieces

Check whether a single-character image is missing the leading $. Without it, MZ expects a standard multi-character layout and divides the canvas into the wrong slots. Next, verify that the sheet width and height produce the intended cell dimensions when divided by 12 and 8.

The walking animation is in the wrong direction

Inspect the grid order and make sure each directional row contains three animation patterns. A drawing can have perfect dimensions but still animate incorrectly if poses were placed in the wrong cells.

The character floats or sinks vertically

Check the leading ! marker before moving the artwork. MZ normally positions a map character 6 pixels above its tile; the marker disables that offset.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The character becomes half-transparent in a bush

First distinguish bush shading from PNG alpha. Test the file on a non-bush tile and inspect the source alpha channel. If the image is solid outside the bush but shaded inside it, add the leading ! when you want to suppress that bush behavior.

The image looks blurry

For a flexible-size image, check whether its horizontal width is odd. The manual warns that odd widths can produce blur in the categories covered by that warning and recommends an even width. For a character sheet or tileset, also confirm that the image is being divided into the intended integer cell size.

The tiles do not line up with the map

Check the project’s configured tile size. MZ supports 16-, 24-, 32-, and 48-pixel choices according to the 1.5.0 announcement. Rebuild or resize the tileset around the project’s actual setting rather than assuming the documented 48-pixel standard applies unchanged.

Using MZ’s Bitmap information when diagnosing assets

MZ’s API documentation describes Bitmap as the basic image object and includes width, height, and alpha-pixel inspection functionality. Plugin authors and advanced troubleshooters can use those properties to confirm what the engine loaded: the actual canvas dimensions, whether a file was imported at the expected size, and whether pixels contain alpha data.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

This inspection is useful when an editor preview and the game disagree. A loaded bitmap with the wrong width or height points to an import, export, or filename-layout problem; alpha inspection helps separate genuinely transparent pixels from the bush effect controlled by the character marker.

Quick Recap

SaleBestseller No. 2
Bestseller No. 3
The SNES Pixel Book
The SNES Pixel Book
Spot-varnished 3mm protective board slipcase; Spot-varnished cover; Sewn binding; Shrink-wrapped
$48.99

Quick pre-import checklist

  • The file is encoded as PNG.
  • The asset category is identified before choosing dimensions.
  • Battlebacks, face cells, and title images follow their documented sizes.
  • Character sheets divide cleanly into 12 columns and 8 rows.
  • Character cells use a consistent size and contain four directions with three patterns.
  • $ is present for a single-character sheet.
  • ! is present when the default map offset and bush half-transparency should be disabled.
  • Flexible-size images use an even horizontal width where the manual’s blur warning applies.
  • The project’s tile-size setting has been checked before creating tileset artwork.
  • Transparency has been tested both in the PNG and in the in-game scene.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.