The places where pixel art goes wrong are surprisingly predictable. "The face is unrecognizable." "The colors look dirty." "I'll never finish placing all these tiles." Most of the moments when work grinds to a halt in Design Studio fall into one of the fourteen symptoms covered here. And nearly all of them come down not to skill, but to the order in which you adjust settings and the source image you started from.
This page is organized so you can look up a problem by its symptom. For every case, the cause is explained first, then the concrete fix. Understanding the cause is what lets you diagnose the next, slightly different problem on your own. Feel free to skip straight to whichever heading matches what you are seeing.
Before the individual cases, one principle that applies to all of them. When a result looks wrong, most people immediately start flipping between conversion methods or raising and lowering the canvas precision. That usually means changing settings without ever identifying the cause. Work through this order instead.
Simply following this order prevents the common state of being lost, where you no longer know which change produced which effect. As you read the cases below, keep asking whether the cause lies upstream (the image, the crop) or downstream (the conversion settings).
A pixel art canvas lives at a resolution orders of magnitude lower than a photograph. We recognize faces from the spatial relationship between small parts — eyes, nose, mouth — so when only a handful of dots are available for those parts, the brain can no longer assemble them into a face. If the face occupies only about a tenth of your source image, it shrinks to just a few tiles after conversion. There are two fixes. First, crop so the face fills the frame, discarding the body and background without hesitation. If that still isn't enough, choose a canvas with higher precision (more dots). Including the whole body and capturing a recognizable likeness are mutually exclusive goals. Decide which one matters first.
Conversion picks the nearest color from a palette, so the brightness distribution of your source image carries straight through to the result. Dark photos, or shots taken under an overcast sky, cluster into the darker midtones and the whole piece looks sunken. Conversely, applying a method that lifts brightness to an already bright image pushes the highlights against the ceiling and they clip to white. If the result looks dull, try Method 3 (High Contrast), or use Method 2 to lift brightness and contrast. If that still isn't enough, correcting the brightness of the original image and re-uploading is the reliable route. If colors are blowing out instead, the first move is to go back to Method 1 (Standard). Methods 2 and 3 exist precisely to raise brightness and saturation, so on bright source material they overshoot. The rule of thumb — the brighter the source, the more Method 1 suits it — will rarely steer you wrong.
When the subject and background are close in color, conversion assigns both to the same palette color and the outline disappears. A difference your eye could resolve in the photo — a white shirt against a light gray wall — becomes a single color the moment the palette is narrowed. The cleanest fix is to use background removal during conversion and take the background out entirely. If you want to keep the background, change the crop so it includes something with a real brightness difference from the subject (a dark wall, the sky), or use Method 3 to exaggerate contrast and saturation until a difference exists. Note that heavy color reduction dissolves weak boundaries even further, so go easy on it for images where the edges are already fragile.
Text vanishes — or breaks into a scattering of disconnected dots — the moment its stroke width drops below one tile. Check patterns, lace, thin lettering in a logo: the information is already lost at the point of downscaling, so no conversion method can bring it back. This is a physical limit, not a settings problem. The realistic solution is to give up on the detail and remove it. Flattening a fine pattern into a single color looks far better than a spray of illegible specks. If you truly need text, it is more reliable to redraw it by hand after conversion using the pen in Design Edit mode, thinking in terms of a heavy typeface. Allow at least about five tiles of height per character.
Every photograph contains color fluctuation (noise) below the threshold of conscious perception. You never notice it at normal size, but once the image is converted, each tile gets its own color assignment and isolated dots scatter across surfaces that ought to be smooth. The effect is strongest in photos taken in low light or images that have been compressed by social media. The fix is to raise noise reduction to "Medium". Try Medium first, and move to "High" only if speckles remain. Be aware that High also flattens genuine detail, so for pieces with faces or fine ornamentation it is safer to stop at Medium. Isolated dots that noise reduction alone won't remove tend to be absorbed into their surroundings when you strengthen step 2 of color reduction (merging similar colors).
Working inside the game costs you effort every time you switch colors. As a result, your working time depends far more on the number of colors than on the total number of tiles. A 40-color blueprint doesn't feel twice as heavy as a 20-color one — it feels considerably worse than that. A comfortable working range is 15 to 25 colors. If you are above that, consider reducing. The efficient procedure is to apply step 1 (removing the least-used colors) fairly aggressively first. A color used in only a few tiles barely changes the impression of the piece when it disappears, yet it demands a full color's worth of labor during construction. Then use step 2 (merging similar colors) to tidy up the overall palette. Doing this in the reverse order tends to leave scattered minor colors behind after merging, forcing you to repeat the work. To finish, if there are specific colors you want to keep or eliminate, use "Custom" and tap a color to merge it manually into its nearest neighbor.
Smooth transitions like sky or skin get broken down, during assignment to a limited palette, into stretches of identical color separated by abrupt edges. That is banding. It stands out because those straight boundaries do not exist in nature. The fix is counter-intuitive: strengthen step 2 of color reduction and use fewer colors. A half-preserved gradient reads as banding, but if you commit and cut it down to two or three steps, the brain reinterprets it as deliberate shading and it starts to look like proper pixel art. On top of that, alternating tiles along a boundary in a checkerboard pattern lets them blend into an intermediate tone when viewed from a distance. This is worth doing by hand with the pen in Design Edit mode.
Every tile in pixel art has to hold some color. There is no way to carry "transparent" through as a state, so transparent areas are replaced by an opaque color during conversion. What you see as black or white is that replacement. It is not a bug — it is transparency information being turned into a color. The fix is to use background removal during conversion to drop the background you no longer need. Alternatively, a reliable approach is to composite the transparent PNG over your preferred background color in an image editing app, export that, and upload the flattened image. The same behavior applies when you layer transparent material with Insert Image in Design Edit mode, so check the preview before confirming the placement.
On a phone, your finger covers the very dot you are touching, so it is hard to see where you actually are. On top of that, when you try to position an inserted image, the browser sometimes confuses page scrolling with dragging the image. That is behind most cases of "I can't put it where I want it." The trick is not to aim for precision immediately — make large movements first to establish the rough position. Then adjust zoom and rotation, and only fine-tune at the end. Placing your finger and pausing for a beat before moving makes it less likely to be read as a scroll. Temporarily lowering the opacity lets you see the artwork underneath, which makes alignment far more accurate. For pieces you intend to build seriously, using a larger screen — a computer or tablet — ends up being faster overall.
Saving a piece to your account requires being logged in. If you work without logging in, the save never completes, and the content can be lost the moment you leave the page. By far the most common explanations behind "it disappeared" are that it was never saved in the first place, or that you were logged in under a different account. Start by checking your login status. Next check your connection, and if you are somewhere with a weak signal, move to a stable network, refresh the browser and try again. For long sessions, building a habit of saving at every natural break keeps any loss small. If you still can't save, please get in touch through the contact form and include the device and browser you are using.
Share URLs are long strings, so pasting one into social media or a messaging app can introduce a line break partway through, or clip the end, leaving a link that no longer works. First check whether any part of the URL is missing or whether stray characters have crept in. Copying the link again and pasting it directly into the browser's address bar is a good way to isolate the cause. If the page comes up blank, check your connection, then refresh (reload) the browser and try once more. Testing whether it opens on a different device or browser tells you whether the problem is on your device's side. If none of that resolves it, please contact us through the contact form and include the URL that failed to open.
This is not a malfunction. Public works in the Community Gallery are published only after an administrator reviews them, so they do not appear immediately after submission. Please check back after some time has passed. Note also that works using images, logos or characters owned by someone else without permission cannot be published. If you submitted a piece based on existing material and it never appeared, it is worth checking whether this applies. One more thing that is easy to overlook: pieces created in Free Canvas mode. Works made at arbitrary sizes in Free Canvas are not published to the Community Gallery. If you are creating something with gallery submission in mind, choose a canvas that corresponds to an in-game design frame from the very start.
The blueprint on your screen and the finished object in the game are seen under completely different conditions. You view the blueprint enlarged and head-on; in the game it is applied to a three-dimensional outfit or decoration and seen small, from a normal distance. From a distance, fine detail dissolves and disappears — only the silhouette and the light-dark contrast survive. To close that gap, step back from your screen while still at the blueprint stage, or shrink the display and check it that way. If you can't tell what the picture is at that size, you won't be able to in-game either. The countermeasures are to place the main subject large and to establish a clear brightness difference against the background. Darkening the outline by one step does more than adding more fine detail ever will. Also remember that arbitrary-size pieces made in Free Canvas mode may not fit the in-game frames, so if the piece is destined for the game, pick a corresponding canvas from the beginning.
This is a problem of work design, not willpower. Work with no visible end stalls because you get no sense of progress. The remedy comes down to breaking the work into small pieces and making progress visible. Block Work mode lets you advance in units of 10×10 tiles and saves your progress, so you can build in a way that assumes interruption and resumption. Deciding "just three blocks today" makes each session's cost predictable, and stopping midway no longer means losing your place. If you prefer to lay down one color at a time, Standard Work mode suits you better; the per-color highlight lets you follow only the tiles of that color without getting lost. And the single most effective measure is to narrow the palette to 15–25 colors before you begin. The workload is essentially fixed before you start. A piece that gets finished is a piece that was designed at a size you could finish.
The one move worth remembering: when something just looks "messy", before you start switching conversion methods, try setting noise reduction to Medium and applying step 1 of color reduction firmly. In practice, a large share of the visual complaints people have with this tool improve from that single move alone. Fewer colors not only tidy up the picture — they lighten the building work at the same time.
If you have tried everything here and the problem persists, or if you are seeing something not covered on this page, please don't hesitate to get in touch. You can reach us through the contact form. When you do, including the device you're using (iPhone / Android / computer), the browser, and what happened after which action makes it far quicker to identify the cause. A screenshot of the screen is also a great help if you can provide one.
You can also send reports and requests to the developer's X (formerly Twitter) account, @kaorupia. Design Studio is a free tool that keeps improving little by little based on the feedback people send in. Even a simple "this part was confusing" becomes a hint for the next improvement.