Free tools Windows power users keep installed
One-click scans. No signup required.
RPG Maker MZ expects image assets in PNG format, but it does not impose one universal canvas size. The correct dimensions depend on whether you are importing a face, character sheet, battleback, title image, tileset, picture, parallax, or enemy graphic. Character sheets are divided into a fixed grid, filename prefixes can change character positioning and bush behavior, and tile dimensions follow the setting selected for the project.
The safest workflow is to identify the asset category first, apply its documented size or grid rule, check the PNG alpha channel, and then verify the project’s tile-size setting before exporting tiles. The specifications below are for RPG Maker MZ; other RPG Maker versions can use different rules.
As an Amazon Associate I earn from qualifying purchases.
What image format does RPG Maker MZ use?
The RPG Maker MZ Help documentation states: “All images must be in the PNG format.” This rule covers the image categories used by the engine, including faces, characters, pictures, parallaxes, battlebacks, tilesets, title screens, and enemy graphics.
Recommended Free Tools
Use a genuine .png file rather than simply renaming a JPEG or another format. PNG preserves the alpha channel needed for irregular sprite silhouettes, UI elements, and other images that must show the map or battle scene through transparent pixels. A file can have the right extension and still be unsuitable if it was exported without transparency or has been damaged by a conversion utility.
RGB versus RGBA PNGs
Opaque artwork can be stored as a PNG without transparent pixels. Artwork that needs cutout edges, holes, shadows, or partially transparent pixels should be exported with an alpha channel (normally RGBA). MZ reads pixel alpha through its bitmap system, so transparent and semitransparent pixels are part of the image data rather than a special color-key setting.
Which RPG Maker MZ images have fixed dimensions?
Only some asset categories have a prescribed canvas size. The following values come from MZ’s Asset Standards documentation.
| Asset category | Required or documented size | How to interpret it |
|---|---|---|
| Battlebacks | 1000×740 pixels | Use this canvas for the battleback image category. |
| Face graphics | 144×144 pixels per face | Faces are arranged in 2 rows by 4 columns, making a complete sheet 576×288 pixels. |
| Title-screen images | 816×624 pixels | This is the documented MZ title-screen image size. |
| Front-view enemy images | Any size | The manual permits flexible dimensions; size the artwork for the composition you need. |
| Pictures | Any size | MZ can display a picture at a chosen size, subject to how your event or plugin positions and scales it. |
| Parallaxes | Any size | The image can be sized for the map and parallax behavior you configure. |
| Side-view enemy images | Any size | There is no single prescribed canvas in the manual. |
The word “any” does not mean that every size will look equally good. Your event coordinates, scaling choices, camera composition, and the image’s intended repeat or crop behavior still determine a practical size. The manual also warns that odd horizontal widths can appear blurred for categories where that caveat is given. When an image falls under that warning, use an even pixel width and inspect it in-game instead of relying only on an image editor’s preview.
Face sheets: calculate the full file size
A face slot is 144×144 pixels. MZ reads eight slots in a two-by-four arrangement: four columns across and two rows down. Therefore, a conventional complete face sheet is 4 × 144 = 576 pixels wide and 2 × 144 = 288 pixels high. If a face appears cropped or the wrong expression is selected, check the sheet dimensions and the slot order before changing the portrait itself.
How character sprite sheets are divided
Character sheets follow a grid rather than a single image-size rule. One map character has four walking directions and three animation patterns per direction. That is 12 cells for each character. In the standard MZ arrangement, a multi-character sheet contains eight characters, so the sheet has 8 × 12 = 96 cells arranged as 12 columns by 8 rows.
Standard 48-pixel cells
The normal cell is 48×48 pixels. A standard eight-character sheet is consequently 12 × 48 = 576 pixels wide and 8 × 48 = 384 pixels high. The important rule is not the nominal canvas size; it is that the sheet divides cleanly into the expected grid and that each character’s frames occupy the correct positions.
Variable cell sizes
MZ can use character cells other than 48×48. The engine calculates a cell’s width as one-twelfth of the entire sheet width and its height as one-eighth of the entire sheet height. For example, a sheet that is 768 pixels wide and 512 pixels high produces 64×64 cells (768 ÷ 12 = 64; 512 ÷ 8 = 64). Every frame must still align to that calculated grid. A sheet with inconsistent frame sizes cannot be repaired by changing a filename marker; the artwork must be rebuilt on a consistent grid.
Single-character sheets and the dollar sign
A leading dollar sign ($) tells MZ that the file contains one character instead of the normal eight-character sheet. The engine still uses four directions by three patterns, but it divides the image into the single-character layout. Without the marker, a single-character image is interpreted as part of a larger sheet and will appear shrunken, offset, or otherwise misaligned.
The exclamation mark and map positioning
By default, MZ displays a map character six pixels above its tile. A leading exclamation mark (!) disables that six-pixel shift. The same marker also prevents bush elements from making the character appear half-transparent. This is an engine behavior, not a transparency setting inside the PNG.
The markers can be combined. A filename beginning with !$ identifies a single-character sheet that should be drawn without the usual vertical offset and without the bush half-transparency behavior. The markers must be at the beginning of the filename; placing them after other characters does not give the intended result.
What tile size should you use?
Do not assume that every MZ project uses 48-pixel tiles. The MZ 1.5.0 release announcement lists selectable tile sizes of 16, 24, 32, and 48 pixels. The Asset Standards documentation describes 48×48 as the standard, but the project setting can select one of the other documented sizes.
Before drawing or resizing a tileset, open the project’s database or system settings and confirm the tile-size value selected by that project. A tileset designed for 48-pixel cells will not align correctly in a 32-pixel project, even though both files are valid PNGs. The tile-size list is specifically documented for MZ 1.5.0; check the installed version and project settings rather than assuming that every future update exposes exactly the same choices.
Tile-size checks before export
- Read the project’s selected tile size instead of inferring it from an unrelated sample map.
- Make every tile cell an exact multiple of that value.
- Keep terrain edges, autotile patterns, and collision-relevant borders aligned to the same grid.
- Preview the tileset on a test map at 100 percent scale so a scaling error is not mistaken for an artwork problem.
PNG transparency versus MZ bush transparency
There are two separate reasons a character can look transparent. The first is ordinary PNG alpha: pixels in the file may be fully transparent, partially transparent, or opaque. Inspect the image on a checkerboard background and verify that the artwork was exported with the intended alpha values.
The second is MZ’s bush effect. When a character stands on a tile configured as a bush, the engine can render the lower portion of the character with a half-transparent appearance. This effect can occur even when every visible pixel in the PNG is fully opaque. A leading ! in the character filename prevents that bush treatment and also removes the six-pixel vertical offset.
Diagnosing an apparently faded sprite
- Open the PNG in an editor that displays alpha and check whether the lower body is actually semitransparent in the file.
- Place the character on an ordinary non-bush tile. If the fading disappears, the map tile behavior was responsible.
- If the character must remain fully opaque on bush tiles, add the leading
!marker and test the resulting vertical alignment. - If the entire sprite is faded everywhere, inspect the PNG export, the event’s opacity settings, and any visual effects or plugins separately from the filename markers.
A reliable asset-preparation workflow
Use this sequence whenever you create or import an image.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Classify the asset. Decide whether it is a face, character sheet, battleback, title image, tileset, picture, parallax, front-view enemy, or side-view enemy. The category determines whether a fixed dimension, grid, or flexible canvas applies.
- Set the canvas. Use 1000×740 for a battleback, 816×624 for a title-screen image, and 144×144 per face in a 4-by-2 face sheet. For flexible categories, choose a size that suits the intended crop, repeat, and display scale.
- Build the correct grid. For a standard character sheet, use 12 columns by 8 rows with 48-pixel cells. For another cell size, make the complete sheet width divisible by 12 and height divisible by 8.
- Confirm the tile setting. Read the project’s selected tile size before exporting tilesets; do not substitute the 48-pixel standard automatically.
- Export as PNG. Preserve alpha for cutout artwork and verify that the exported file is genuinely PNG.
- Choose filename markers deliberately. Use
$for one character,!to remove the map offset and bush effect, and!$when both behaviors are required. - Test in MZ. Import the file into the matching asset folder, place it in a small test map or battle, and inspect alignment, cropping, sharpness, and transparency at the project’s normal display scale.
Common problems and precise fixes
The sprite is split, tiny, or shows the wrong frames
This usually means the sheet grid does not match the filename and canvas. Use $ for a one-character sheet. Otherwise, provide the expected 12-by-8 cell arrangement for a standard multi-character sheet. For custom cells, verify that the width divides by 12 and the height by 8 with no remainder.
The character floats above the ground
MZ normally places map characters six pixels above their tile. If the artwork was drawn to sit directly on the tile, add the leading ! marker rather than resizing the image. Test the feet position on several terrain types after making the change.
The lower body becomes translucent in a bush
First distinguish PNG alpha from the bush effect. If the file is opaque but the lower body fades only on bush tiles, use the leading ! marker when that effect is not wanted. If fading occurs everywhere, repair the alpha channel or investigate event and plugin opacity settings.
The image looks soft or blurred
Check whether the file has an odd horizontal width in a category for which the manual warns about blur. Re-export with an even width where applicable, then test at the project’s display scale. Also confirm that the image is not being enlarged or reduced by an event, screen-resolution setting, or plugin.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →A face portrait is cropped or selected incorrectly
Check that each face occupies exactly 144×144 pixels and that the sheet uses four columns and two rows. A complete conventional sheet should be 576×288 pixels. Reposition the portrait inside its slot instead of supplying a different overall size.
The tileset does not line up with the map
Read the project’s tile-size setting and compare it with the grid used to draw the tileset. Rebuild or resize the artwork to the selected 16-, 24-, 32-, or 48-pixel cell size documented for MZ 1.5.0. Scaling a mismatched tileset after the fact can create soft edges and incorrect collision boundaries.
What MZ’s Bitmap system tells you about image debugging
MZ’s API documentation describes Bitmap as the basic image object and exposes width and height information along with alpha-pixel inspection functionality. That matters when a runtime or plugin diagnostic reports a size or transparency problem: verify the bitmap’s actual dimensions and alpha data, not just the filename or what an image editor appears to show.
For a systematic check, compare five things: the asset category, the file’s pixel dimensions, the expected sheet grid, the project’s tile-size setting, and the filename markers. Then determine whether MZ is cropping or looping the image as part of its intended display behavior. This separates an invalid asset from a valid asset being displayed with a scale, crop, parallax, bush, or event setting you did not expect.
Quick Recap
Quick decision guide
- If the question is format, use PNG and preserve alpha where transparency is needed.
- If the question is a fixed size, apply the category rule: 1000×740 battlebacks, 144×144 face slots in a 4-by-2 sheet, and 816×624 title images.
- If the question is a character sheet, check the 4-direction, 3-pattern layout, then confirm whether the file is an eight-character sheet or a single-character
$sheet. - If the question is a floating or bush-affected character, test the leading
!marker before editing the artwork. - If the question is a tileset, read the project’s selected tile size first; 48 pixels is standard documentation, not a universal requirement.
- If the question is blur, inspect horizontal width and display scaling, especially where the manual flags odd widths.
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.
