Your art glows on screen but not in life: gamma without the lecture

Gamma 2.2 and sRGB—what to remember

Do not confuse with brightness

In “Gamma 2.2 and sRGB—what to remember,” the block on do not confuse with brightness is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about do not confuse with brightness, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

When a deadline hits, “Do not confuse with brightness” is the first cut. Then you pay for reprints or fix color overnight. I budget ten minutes for this on every commercial export—cheaper than one botched run. Beginners need fifteen on a study sheet, not commerce.

Section “Gamma 2.2 and sRGB—what to remember” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Do not confuse with brightness” to a simple still life—mug, book, lamp. A complex character can wait. On a mug you see line, tone, and export mistakes; on a dragon everything gets blamed on “not my style.”

Pair with online editor guide: after “Do not confuse with brightness,” open a short bit of the neighbor article and repeat one move on your canvas. That is how scattered topics stick—otherwise each guide lives alone and dies in a week.

I mention free drawing apps not to tick a box but as a neighbor tool to “Do not confuse with brightness.” Open both tabs only while you practice: read one paragraph, do one step on the canvas. Otherwise reading replaces drawing and everything feels clear until export.

Monitor profile

In “Gamma 2.2 and sRGB—what to remember,” the block on monitor profile is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about monitor profile, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

When we work through “Monitor profile,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

When a deadline hits, “Monitor profile” is the first cut. Then you pay for reprints or fix color overnight. I budget ten minutes for this on every commercial export—cheaper than one botched run. Beginners need fifteen on a study sheet, not commerce.

Section “Gamma 2.2 and sRGB—what to remember” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Monitor profile” to a simple still life—mug, book, lamp. A complex character can wait. On a mug you see line, tone, and export mistakes; on a dragon everything gets blamed on “not my style.”

Pair with layers in the editor: after “Monitor profile,” open a short bit of the neighbor article and repeat one move on your canvas. That is how scattered topics stick—otherwise each guide lives alone and dies in a week.

HDR is another story

In “Gamma 2.2 and sRGB—what to remember,” the block on hdr is another story is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about hdr is another story, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

If “HDR is another story” feels minor, compare two versions of one file: before and after the fix. I show students that export, color, and sheet size are linked. A 5% brightness shift or ten millimeters of bleed sometimes decides whether print accepts the job or sends questions back.

Before bed after “HDR is another story” I ask: what can I reproduce tomorrow without the article? If the answer is only “open the page,” there was too little practice. One repeated step on a fresh canvas beats three paragraphs read.

Homework after “HDR is another story”: one before screenshot, one after, a three-word caption—what changed. Without captions a “final_v2” folder is meaningless in a month. That builds hand and eye memory, not just a list of internet tips.

When we work through “HDR is another story,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

Setup without hardware

Test strips

In “Setup without hardware,” the block on test strips is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about test strips, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

If “Test strips” feels minor, compare two versions of one file: before and after the fix. I show students that export, color, and sheet size are linked. A 5% brightness shift or ten millimeters of bleed sometimes decides whether print accepts the job or sends questions back.

Before bed after “Test strips” I ask: what can I reproduce tomorrow without the article? If the answer is only “open the page,” there was too little practice. One repeated step on a fresh canvas beats three paragraphs read.

Homework after “Test strips”: one before screenshot, one after, a three-word caption—what changed. Without captions a “final_v2” folder is meaningless in a month. That builds hand and eye memory, not just a list of internet tips.

When we work through “Test strips,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

Room brightness

In “Setup without hardware,” the block on room brightness is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about room brightness, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

I mention resolution and DPI not to tick a box but as a neighbor tool to “Room brightness.” Open both tabs only while you practice: read one paragraph, do one step on the canvas. Otherwise reading replaces drawing and everything feels clear until export.

Mistakes in “Room brightness” rarely show on a phone preview. Open the file on your main screen, step back, squint—the squint test from traditional painting works for dpi and gamma too. Use the phone to remind you to download a backup, not as final judge.

A common trap in “Room brightness” is comparing your setup to someone’s YouTube rig: different monitor, paper, software. Compare yesterday’s you to today’s you on the same file. I keep a “reference of the week”—one PNG I return to when I doubt myself.

Last week in class “Room brightness” came up again—and that is a normal learning loop, not failure. We ran a mini check: canvas size, sRGB profile, one test export, open the file on another device. Two people only needed step two; one needed the export. Practice works as short checks, not an hour lecture.

Viewing angle

In “Setup without hardware,” the block on viewing angle is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about viewing angle, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

Before bed after “Viewing angle” I ask: what can I reproduce tomorrow without the article? If the answer is only “open the page,” there was too little practice. One repeated step on a fresh canvas beats three paragraphs read.

Homework after “Viewing angle”: one before screenshot, one after, a three-word caption—what changed. Without captions a “final_v2” folder is meaningless in a month. That builds hand and eye memory, not just a list of internet tips.

When we work through “Viewing angle,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

When a deadline hits, “Viewing angle” is the first cut. Then you pay for reprints or fix color overnight. I budget ten minutes for this on every commercial export—cheaper than one botched run. Beginners need fifteen on a study sheet, not commerce.

Windows and macOS: where to click

Night Light off while working

In “Windows and macOS: where to click,” the block on night light off while working is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about night light off while working, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

Homework after “Night Light off while working”: one before screenshot, one after, a three-word caption—what changed. Without captions a “final_v2” folder is meaningless in a month. That builds hand and eye memory, not just a list of internet tips.

When we work through “Night Light off while working,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

When a deadline hits, “Night Light off while working” is the first cut. Then you pay for reprints or fix color overnight. I budget ten minutes for this on every commercial export—cheaper than one botched run. Beginners need fifteen on a study sheet, not commerce.

Section “Windows and macOS: where to click” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Night Light off while working” to a simple still life—mug, book, lamp. A complex character can wait. On a mug you see line, tone, and export mistakes; on a dragon everything gets blamed on “not my style.”

Two monitors

In “Windows and macOS: where to click,” the block on two monitors is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about two monitors, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

Homework after “Two monitors”: one before screenshot, one after, a three-word caption—what changed. Without captions a “final_v2” folder is meaningless in a month. That builds hand and eye memory, not just a list of internet tips.

When we work through “Two monitors,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

When a deadline hits, “Two monitors” is the first cut. Then you pay for reprints or fix color overnight. I budget ten minutes for this on every commercial export—cheaper than one botched run. Beginners need fifteen on a study sheet, not commerce.

Section “Windows and macOS: where to click” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Two monitors” to a simple still life—mug, book, lamp. A complex character can wait. On a mug you see line, tone, and export mistakes; on a dragon everything gets blamed on “not my style.”

Display tablet as second screen

In “Windows and macOS: where to click,” the block on display tablet as second screen is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about display tablet as second screen, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

Section “Windows and macOS: where to click” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Display tablet as second screen” to a simple still life—mug, book, lamp. A complex character can wait. On a mug you see line, tone, and export mistakes; on a dragon everything gets blamed on “not my style.”

Pair with monitor calibration: after “Display tablet as second screen,” open a short bit of the neighbor article and repeat one move on your canvas. That is how scattered topics stick—otherwise each guide lives alone and dies in a week.

I mention line stabilization and pressure not to tick a box but as a neighbor tool to “Display tablet as second screen.” Open both tabs only while you practice: read one paragraph, do one step on the canvas. Otherwise reading replaces drawing and everything feels clear until export.

Mistakes in “Display tablet as second screen” rarely show on a phone preview. Open the file on your main screen, step back, squint—the squint test from traditional painting works for dpi and gamma too. Use the phone to remind you to download a backup, not as final judge.

Soft proof and “print on screen”

Limits

In “Soft proof and “print on screen”,” the block on limits is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about limits, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

If “Limits” feels minor, compare two versions of one file: before and after the fix. I show students that export, color, and sheet size are linked. A 5% brightness shift or ten millimeters of bleed sometimes decides whether print accepts the job or sends questions back.

Before bed after “Limits” I ask: what can I reproduce tomorrow without the article? If the answer is only “open the page,” there was too little practice. One repeated step on a fresh canvas beats three paragraphs read.

Homework after “Limits”: one before screenshot, one after, a three-word caption—what changed. Without captions a “final_v2” folder is meaningless in a month. That builds hand and eye memory, not just a list of internet tips.

When we work through “Limits,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

CMYK preview

In “Soft proof and “print on screen”,” the block on cmyk preview is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about cmyk preview, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

Mistakes in “CMYK preview” rarely show on a phone preview. Open the file on your main screen, step back, squint—the squint test from traditional painting works for dpi and gamma too. Use the phone to remind you to download a backup, not as final judge.

A common trap in “CMYK preview” is comparing your setup to someone’s YouTube rig: different monitor, paper, software. Compare yesterday’s you to today’s you on the same file. I keep a “reference of the week”—one PNG I return to when I doubt myself.

Last week in class “CMYK preview” came up again—and that is a normal learning loop, not failure. We ran a mini check: canvas size, sRGB profile, one test export, open the file on another device. Two people only needed step two; one needed the export. Practice works as short checks, not an hour lecture.

With a kid or teen, teach “CMYK preview” as a game: spot three differences between two prints, guess which file has fewer pixels. With adults, be stricter: a notebook table “cm → px → dpi.” Same logic, different tone.

When to trust it

In “Soft proof and “print on screen”,” the block on when to trust it is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about when to trust it, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

Homework after “When to trust it”: one before screenshot, one after, a three-word caption—what changed. Without captions a “final_v2” folder is meaningless in a month. That builds hand and eye memory, not just a list of internet tips.

When we work through “When to trust it,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

When a deadline hits, “When to trust it” is the first cut. Then you pay for reprints or fix color overnight. I budget ten minutes for this on every commercial export—cheaper than one botched run. Beginners need fifteen on a study sheet, not commerce.

Section “Soft proof and “print on screen”” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “When to trust it” to a simple still life—mug, book, lamp. A complex character can wait. On a mug you see line, tone, and export mistakes; on a dragon everything gets blamed on “not my style.”

Link to tablet calibration

Mapping area

In “Link to tablet calibration,” the block on mapping area is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about mapping area, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

Homework after “Mapping area”: one before screenshot, one after, a three-word caption—what changed. Without captions a “final_v2” folder is meaningless in a month. That builds hand and eye memory, not just a list of internet tips.

When we work through “Mapping area,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

When a deadline hits, “Mapping area” is the first cut. Then you pay for reprints or fix color overnight. I budget ten minutes for this on every commercial export—cheaper than one botched run. Beginners need fifteen on a study sheet, not commerce.

Section “Link to tablet calibration” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Mapping area” to a simple still life—mug, book, lamp. A complex character can wait. On a mug you see line, tone, and export mistakes; on a dragon everything gets blamed on “not my style.”

Parallax vs gamma

In “Link to tablet calibration,” the block on parallax vs gamma is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about parallax vs gamma, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

Mistakes in “Parallax vs gamma” rarely show on a phone preview. Open the file on your main screen, step back, squint—the squint test from traditional painting works for dpi and gamma too. Use the phone to remind you to download a backup, not as final judge.

A common trap in “Parallax vs gamma” is comparing your setup to someone’s YouTube rig: different monitor, paper, software. Compare yesterday’s you to today’s you on the same file. I keep a “reference of the week”—one PNG I return to when I doubt myself.

Last week in class “Parallax vs gamma” came up again—and that is a normal learning loop, not failure. We ran a mini check: canvas size, sRGB profile, one test export, open the file on another device. Two people only needed step two; one needed the export. Practice works as short checks, not an hour lecture.

With a kid or teen, teach “Parallax vs gamma” as a game: spot three differences between two prints, guess which file has fewer pixels. With adults, be stricter: a notebook table “cm → px → dpi.” Same logic, different tone.

Pre-deadline check

In “Link to tablet calibration,” the block on pre-deadline check is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about pre-deadline check, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

I mention resolution and DPI not to tick a box but as a neighbor tool to “Pre-deadline check.” Open both tabs only while you practice: read one paragraph, do one step on the canvas. Otherwise reading replaces drawing and everything feels clear until export.

Mistakes in “Pre-deadline check” rarely show on a phone preview. Open the file on your main screen, step back, squint—the squint test from traditional painting works for dpi and gamma too. Use the phone to remind you to download a backup, not as final judge.

A common trap in “Pre-deadline check” is comparing your setup to someone’s YouTube rig: different monitor, paper, software. Compare yesterday’s you to today’s you on the same file. I keep a “reference of the week”—one PNG I return to when I doubt myself.

Last week in class “Pre-deadline check” came up again—and that is a normal learning loop, not failure. We ran a mini check: canvas size, sRGB profile, one test export, open the file on another device. Two people only needed step two; one needed the export. Practice works as short checks, not an hour lecture.

Checklist before sending to a client

sRGB export

In “Checklist before sending to a client,” the block on srgb export is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about srgb export, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

If “sRGB export” feels minor, compare two versions of one file: before and after the fix. I show students that export, color, and sheet size are linked. A 5% brightness shift or ten millimeters of bleed sometimes decides whether print accepts the job or sends questions back.

Before bed after “sRGB export” I ask: what can I reproduce tomorrow without the article? If the answer is only “open the page,” there was too little practice. One repeated step on a fresh canvas beats three paragraphs read.

Homework after “sRGB export”: one before screenshot, one after, a three-word caption—what changed. Without captions a “final_v2” folder is meaningless in a month. That builds hand and eye memory, not just a list of internet tips.

When we work through “sRGB export,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

Mini print at home

In “Checklist before sending to a client,” the block on mini print at home is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about mini print at home, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

Homework after “Mini print at home”: one before screenshot, one after, a three-word caption—what changed. Without captions a “final_v2” folder is meaningless in a month. That builds hand and eye memory, not just a list of internet tips.

When we work through “Mini print at home,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

When a deadline hits, “Mini print at home” is the first cut. Then you pay for reprints or fix color overnight. I budget ten minutes for this on every commercial export—cheaper than one botched run. Beginners need fifteen on a study sheet, not commerce.

Section “Checklist before sending to a client” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Mini print at home” to a simple still life—mug, book, lamp. A complex character can wait. On a mug you see line, tone, and export mistakes; on a dragon everything gets blamed on “not my style.”

Photo in daylight

In “Checklist before sending to a client,” the block on photo in daylight is where theory meets a real file—not a shopping cart. I ask students to name one symptom before changing tools: wobble, muddy gray, wrong export size, or a driver that dropped pressure. Fix that single item, save a dated PNG, and compare to yesterday on the same screen.

Last week this showed up again in class: two people had the same complaint about photo in daylight, but one needed a smaller canvas and the other needed a layer rename. Same heading, different fixes—that is normal. Write three words after the session about what changed; “prettier” is not a metric, “exported without crop” is.

When we work through “Photo in daylight,” I ask you to write down one concrete symptom: what exactly “breaks” on screen or in the file. Without a symptom we fix the wrong thing—buy a pen when the issue is dpi, or tweak brightness when the profile is wrong. After you note it, pick one step for today, not five. Tomorrow take the next if the symptom is still there.

When a deadline hits, “Photo in daylight” is the first cut. Then you pay for reprints or fix color overnight. I budget ten minutes for this on every commercial export—cheaper than one botched run. Beginners need fifteen on a study sheet, not commerce.

Section “Checklist before sending to a client” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Photo in daylight” to a simple still life—mug, book, lamp. A complex character can wait. On a mug you see line, tone, and export mistakes; on a dragon everything gets blamed on “not my style.”

Pair with layers in the editor: after “Photo in daylight,” open a short bit of the neighbor article and repeat one move on your canvas. That is how scattered topics stick—otherwise each guide lives alone and dies in a week.

• Gamma is not the same as brightness;
• sRGB is the default export baseline;
• Turn Night Light off while judging color;
• Soft proof is an approximation, not a guarantee;
• A test print ends arguments.

1. Reset OSD; disable dynamic contrast.
2. Run a grayscale wedge test.
3. Assign an sRGB profile.
4. Night Light off during work.
5. Export a test PNG and check on your main screen.

Gamma correction is explained on Wikipedia.

To compare a test file on another device quickly, open the same PNG via the online editor in a second room—not as a final judge, but as a second glance.

Frequently asked questions

Time to draw, not just read

Theory fades in a couple of days if you never use it. Open the editor and spend 15 minutes on what you just read. That is enough for the skill to stick.

Topics in this guide

• monitor calibration for drawing
• monitor gamma
• screen contrast artist
• monitor color drawing
• monitor setup

← Android for drawing: when your phone feels tight and an iPad is out of budget 300 DPI again: how not to ruin a print with a pretty file →