How to estimate pixels by eye.
Pixel estimation sounds more mysterious than it is. You look at a space, make a guess, measure it, and let the miss teach your eye a little. Pixactly makes that loop hard to ignore: target size first, drawing second, result right after. No inspector panel to lean on.
Keep a few sizes in your head
I would not try to memorize every possible rectangle. That gets boring fast, and it does not really transfer. It is better to keep a few rough sizes in your head. For example, 24px, 48px, 100px, 200px, and 320px are enough to start.
Those numbers have a feel. 24px is close to a small icon. 48px is around the size of many comfortable touch targets. 100px is a small chunk of UI. 320px is not far from an old narrow phone width. These are not rules. They are anchors.
When Pixactly asks for a new rectangle, do not guess from nothing. Compare the target against the closest reference in your mental set. If the width is 180px, picture two 100px blocks with a little taken away. If the height is 64px, picture a 48px control plus a little breathing room.
Do width and height separately
Judging area instead of individual dimensions can hide a miss. A rectangle can feel visually similar while being too wide and too short. Before drawing, say the width and height to yourself as two separate problems. Place the width first, pause, then decide the height. This small habit prevents your eye from averaging the whole shape into a single vague size.
For a 180 × 120px target, picture the width as 200px minus 20px and the height as 100px plus 20px. Check that the width is about one and a half times the height. These are two size anchors and a ratio check; none can substitute for the others.
Use the screen around the shape
Pixel estimation improves when you use surrounding space. Notice the distance from your starting point to the edge of the canvas, the center of the screen, and the game HUD. These landmarks help you scale the target. Designers do the same thing in interfaces: they judge a button by its relationship to nearby labels, margins, and containers.
Keep the same window size and zoom while testing an anchor. After each round, note whether the drawing extends farther than the target on each axis. If widths repeatedly overshoot, your width anchor is worth revisiting. The result shows the miss; it does not establish whether the cause was the anchor, hand movement, or a changed setup.
Choose a correction from direction, not average error
Record too wide / too narrow and too tall / too short during each round's feedback. At the end, use the average width and height errors to choose an axis to inspect. These averages are absolute distances: a 10px width miss could come from either a wider or a narrower drawing. The final summary cannot recover the signed directions for you.
If your notes repeatedly say too wide, try a slightly narrower width anchor. If they say too narrow, try a wider one. If directions alternate, keep the anchor and test a more consistent endpoint or pace first. Apply the same reasoning to height. The width-direction exercise gives a five-round worked example.
Practice in short sets
Five focused rounds are usually better than a long distracted session. Play once, review whether width or height caused more error, then play again with one correction in mind. The goal is not to memorize Pixactly targets. The goal is to make your next visual guess slightly more calibrated than the last one.
Stop after two or three sets if you find yourself chasing the score instead of reading feedback. Come back later and check whether the same direction appears. Targets change between sets, so a single lower total is not enough to establish a lasting improvement.