PC drawing apps: do not install Photoshop on day one—an honest map

Task → app (table)

Sketch and paint

In “Task → app (table),” the block on sketch and paint 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 sketch and paint, 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 “Sketch and paint” 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 “Sketch and paint” 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 “Sketch and paint” 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 “Sketch and paint” 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.

Comics and line art

In “Task → app (table),” the block on comics and line art 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 comics and line art, 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 “Comics and line art,” 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, “Comics and line art” 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 “Task → app (table)” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Comics and line art” 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 “Comics and line art,” 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.

Vector and logos

In “Task → app (table),” the block on vector and logos 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 vector and logos, 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.

A common trap in “Vector and logos” 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 “Vector and logos” 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 “Vector and logos” 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.

If “Vector and logos” 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.

Krita: the free standard

Brushes and stabilizer

In “Krita: the free standard,” the block on brushes and stabilizer 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 brushes and stabilizer, 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 “Krita: the free standard” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Brushes and stabilizer” 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 “Brushes and stabilizer,” 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 “Brushes and stabilizer.” 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 “Brushes and stabilizer” 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.

Layers and masks

In “Krita: the free standard,” the block on layers and masks 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 layers and masks, 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.

A common trap in “Layers and masks” 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 “Layers and masks” 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 “Layers and masks” 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.

If “Layers and masks” 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.

Where beginners trip

In “Krita: the free standard,” the block on where beginners trip 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 where beginners trip, 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 “Where beginners trip”: 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 “Where beginners trip,” 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, “Where beginners trip” 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 “Krita: the free standard” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Where beginners trip” 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.”

GIMP: when it makes sense

Photo and collage

In “GIMP: when it makes sense,” the block on photo and collage 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 and collage, 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.

With a kid or teen, teach “Photo and collage” 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.

If “Photo and collage” 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 “Photo and collage” 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 “Photo and collage”: 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.

Weak spots for painting

In “GIMP: when it makes sense,” the block on weak spots for painting 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 weak spots for painting, 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.

A common trap in “Weak spots for painting” 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 “Weak spots for painting” 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 “Weak spots for painting” 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.

If “Weak spots for painting” 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.

Plugins

In “GIMP: when it makes sense,” the block on plugins 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 plugins, 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.

With a kid or teen, teach “Plugins” 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.

If “Plugins” 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 “Plugins” 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 “Plugins”: 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.

Paid: Clip Studio and Photoshop

Subscription vs one-time

In “Paid: Clip Studio and Photoshop,” the block on subscription vs one-time 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 subscription vs one-time, 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.

A common trap in “Subscription vs one-time” 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 “Subscription vs one-time” 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 “Subscription vs one-time” 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.

If “Subscription vs one-time” 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.

Animation and assets

In “Paid: Clip Studio and Photoshop,” the block on animation and assets 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 animation and assets, 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 “Paid: Clip Studio and Photoshop” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Animation and assets” 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 “Animation and assets,” 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 “Animation and assets.” 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 “Animation and assets” 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.

When it pays off

In “Paid: Clip Studio and Photoshop,” the block on when it pays off 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 it pays off, 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 “When it pays off” 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 “When it pays off” 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 “When it pays off” 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 “When it pays off” 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.

The browser as a full alternative

No install

In “The browser as a full alternative,” the block on no install 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 no install, 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 “No install”: 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 “No install,” 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, “No install” 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 “The browser as a full alternative” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “No install” 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.”

Collaboration

In “The browser as a full alternative,” the block on collaboration 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 collaboration, 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 “The browser as a full alternative” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “Collaboration” 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 “Collaboration,” 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 “Collaboration.” 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 “Collaboration” 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.

Limits

In “The browser as a full alternative,” 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.

Pair with cloud storage for art: after “Limits,” 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 contrast and focus not to tick a box but as a neighbor tool to “Limits.” 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 “Limits” 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 “Limits” 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.

One-evening install plan

One app plus cloud backup

In “One-evening install plan,” the block on one app plus cloud backup 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 one app plus cloud backup, 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 “One app plus cloud backup,” 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, “One app plus cloud backup” 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 “One-evening install plan” can turn into a pile of unrelated tips. I keep one thread on a single study sheet: apply “One app plus cloud backup” 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 “One app plus cloud backup,” 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.

Hotkeys

In “One-evening install plan,” the block on hotkeys 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 hotkeys, 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 “Hotkeys” 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 “Hotkeys” 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 “Hotkeys” 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 “Hotkeys” 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.

First PSD or ORA file

In “One-evening install plan,” the block on first psd or ora file 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 first psd or ora file, 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.

A common trap in “First PSD or ORA file” 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 “First PSD or ORA file” 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 “First PSD or ORA file” 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.

If “First PSD or ORA file” 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.

• Task picks the app, not brand loyalty;
• Krita is a solid free start for painting;
• A browser editor when installs are blocked;
• One app for the first month;
• PSD/ORA master plus PNG backup.

1. Download from the official site.
2. Create an Art folder.
3. Calibrate tablet pressure.
4. Learn five shortcuts.
5. Export PNG.

Free and open-source art tools are outlined on Wikipedia’s FOSS article.

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

• drawing software for computer
• best program for drawing
• krita free
• drawing on windows
• art software for artists

← Your first tablet: why 8,192 pressure levels are not the main question Android for drawing: when your phone feels tight and an iPad is out of budget →