Skip to content

What a printed calendar does to a generated image

AICU is selling 2027 desk calendars built from artist images, and its own sample lists the three decisions that decide whether the print works: a typeface picked from 13 open-licence families, all lettering converted to outlines, and Japan Color 2001 Coated CMYK. None of them are things an image model can do for you.

AI-assisted draft. Reviewed and edited by the Phosphene team before publication.

On this page
A small print calendar on a wooden stand beside a window, its top page curling back to reveal a muted watercolour landscape in green and rust
Twelve months plus a cover. Thirteen pictures, one ink limit, and a trim line you cannot argue with.

AICU, a Japanese creative-AI community, built a browser tool that turns your own pictures into a desk calendar for 2027: twelve months plus a cover, holidays already filled in, printed and shipped inside Japan. They are handing out paper samples at Inter BEE 2026, which runs November 18 to 20, at hall 4, booth 4038 in Makuhari Messe.

The service is not the interesting part. The credit block on the sample calendar is, because it lists how the file was actually built. One typeface, chosen from the thirteen families on AICU's SIL Open Font License list. Every piece of text converted to outlines. Colors specified as Japan Color 2001 Coated CMYK, a Japanese coated-stock standard rather than the word "CMYK" standing in for a real profile. They also note that anyone can rebuild the same submission file by dropping thirteen photos into it.

Those three decisions are the distance between a picture that looks fine on a phone and a picture that survives a press. If you generate images and ever intend to put them on something physical, this is the checklist that gets skipped.

CMYK is a smaller box than your screen, and it has a specific shape

A generated image arrives in sRGB, which can describe colors that no combination of process inks will produce. Saturated cyan-teal, electric blue, and the violet-to-magenta gradients that every model reaches for when asked for something cinematic are the first casualties. They do not fail loudly. The proof comes back slightly muddy in exactly the area the composition was built around.

Japan Color 2001 Coated is worth naming because it makes the failure testable. It is a published characterization of ink on coated paper, so a designer can soft proof against it and see which colors fall outside. "CMYK" on its own is not a target; it is a color mode.

Two checks do most of the work. First, soft proof with the printer's profile and look at the saturated third of the picture, not the whole frame. Second, open the numbers for the darkest region. Generated night scenes tend to crush to near-black, and a large flat black area prints as a dead rectangle unless the file carries enough separation for the press to lay ink in steps.

There is a third thing that only shows up after printing: banding. A smooth generated sky is a long, low-contrast gradient, and gradients are what eight-bit output on paper renders worst. Texture and grain hide it. Clean airbrushed skies do not.

Type is a separate failure, and outlining does not rescue generated lettering

Two different problems share the word "text" in an image workflow, and people solve one while believing they solved the other.

The first is a font dependency. You typeset month names in a font that lives on your laptop, you send a file, the printer's system does not have that font, and the names come back in something else. Converting text to outlines kills that dependency. The file carries shapes, and shapes travel.

AICU's restriction to thirteen open-licence typefaces, and the choice of one of them for the sample, is the commercial half of the same decision. Print that ships to customers needs a licence that covers commercial use. If your workflow embeds the font data in a PDF, that is a separate permission, and handing the font file itself to a printer is a third, so check the licence for each use you actually make. Outlining the text usually removes the second and third requirements, which is one reason the two decisions travel together.

The second problem is that image models draw letterforms they cannot spell. A sign in a generated street scene, a label on a product, a title on a poster: the model produces something that reads as text at thumbnail size and turns into pseudo-lettering the moment it is enlarged. Outlining that does nothing, because there was never a font to begin with. The shapes were already wrong.

The rule that follows is boring and it holds: anything that has to be read comes out of a layout tool, not an image model. Generate the picture with empty space where the type goes, set the type for real, then outline before export. If a generated sign has to stay in frame, treat it as an object in the scene rather than as information the reader is meant to use.

Resolution is a ratio at final size, not a number in the settings

The calendar is postcard-sized, so take a Japanese postcard: 100 by 148 millimetres. At 300 pixels per inch that page wants 1,181 by 1,748 pixels. At a more forgiving 250 ppi it wants 984 by 1,457.

A 1,024-pixel render placed across the 100 mm width lands at 260 ppi, which prints cleanly. The same square stretched to fill the 148 mm height lands at 176 ppi, which is where a face starts looking slightly soft. Nothing about the file changed. The placement did.

This is why arguments about generating at 4K miss the point. The question is not how many pixels the model produced, it is how many of them land on each inch of the page. Push a 1,024 render to a full A4 sheet and you are at 124 ppi across the 210 mm width and 88 ppi down the 297 mm edge, and no upscaler fixes that, because upscalers add plausible texture rather than recovered detail. What they add is often visible as smoothed skin and plastic foliage.

Run the arithmetic before generating, not after. Two numbers, page millimetres and placement, tell you the pixel size you actually need.

Thirteen slots turn a folder of images into a shot list

Twelve months plus a cover is a scope constraint disguised as a product feature. It fixes the count, which fixes the decisions: how many candidates, how much revision, how much of the year is spent choosing.

A calendar also does something a feed cannot. Twelve images sit next to each other for a year, so inconsistency stops being invisible. A palette that drifts by two degrees between March and September, a character whose jaw changes, light that comes from four different directions: all of it reads as sloppiness in a bound object even though each frame looked fine alone. The sample AICU printed takes its thirteen images from one source, the cover art of its own magazine, which is one way to guarantee a shared visual language.

Two practical habits come out of that. Decide the slot count before generating, and write the sequence rather than the image: spring, summer, a repeated character, one month that gets a different treatment on purpose. Then keep the rejects. Picking from forty is easier than fixing thirteen, and the picking is where the consistency gets enforced.

A rights answer has to exist per image

AICU asks for confirmation at upload that you hold the rights to each picture, and collaboration submissions stay unpublished until the calendar's owner reviews and imports them. The invite link lets a family or a class deliver one page each, with a nickname and a line of text, and pages that have not arrived get their own request link.

That is an approval queue wearing a friendly interface, and it exists because the person who pays for the print is the person who answers for what is on it. Generated pictures make that harder in a specific way: the rights question is not only "do I own this file" but "what is in it". A recognisable face, a trademark, a character design that belongs to someone else, a model whose terms restrict commercial use. None of those are answered by the file's metadata.

Keep a record per image, not per project: the model, the prompt, the seed where the tool exposes one, and the licence you were operating under. It takes a minute per keeper and it is the only thing that answers the question six months later when the picture is on a shelf and someone asks where it came from.

The reason they hand out paper at a trade show

AICU's own note says the quiet part: the feel of the paper and the way printed color comes out are things you cannot judge from a screen, which is why the samples are physical and why they want people to pick one up.

That is the whole test. A proof on a monitor is a simulation of a simulation, and the only thing that settles a press job is a printed sheet under the light it will be seen in.

Before paying for anything, run these:

  • Page pixel size at the target ppi, computed from millimetres. For a postcard at 300 ppi, that is 1,181 by 1,748.
  • Soft proof against the printer's named profile, then look at the most saturated part of the image and at the deepest shadows. Saturated areas hit the ink limit first; shadow detail is what a press loses quietly.
  • Every line of type at 100 percent, read out loud. If it is outlined generated lettering, replace it.
  • The trim and bleed rules. Any border or frame you generated may not survive the cut.
  • One physical proof page before the full order. Cheaper than twelve wrong months.

If you want the screen-side versions of these problems, the hi-res fix guide covers what upscaling does and does not recover, and conditioning on a palette is how you keep twelve images in one visual language before print forces the issue.

Sources

Share this guide
X LinkedIn