Octo for color and print in Photoshop

Every file with the right profile, every conversion logged. The ones who approve color on paper are the print shop, with you.

Photoshop converts color per document and, through a UXP script, with the convertProfile method. Octo turns what the print shop asked for into a versioned color contract, checks each file's embedded profile before touching anything, writes the script that converts without touching the source and generates the soft proof with out-of-gamut colors flagged. The printed proof and the release stay with people.

Request an assessment See what it does

convertProfile in UXPsince 23.0according to Adobe's reference

Rendering intents4perceptual, relative, saturation, absolute

Little CMS2.19Apr 17, 2026, MIT license

Sources10listed at the end of the page

What Octo does with your print color.

Six possible deliverables, drawn from the research. None of them saves over the source, all of them check the result by content, and all of them go to whoever answers for prepress.

Color contract per print shop

Destination profile, intent, black point compensation and ink limit per print shop and paper, with the date the print shop confirmed it in writing.

Deliverable: perfis_grafica.json with history

Embedded profile check

Mode, profile and profile class of each file, read without changing anything. A file without a profile becomes a question, not an assumption.

Deliverable: conferencia_cor.csv with sha256

Batch conversion by script

A UXP script that duplicates, converts using the contract, saves a copy with the profile in a new folder and closes the source without saving, with the designer at the workstation.

Deliverable: ConverterPerfil.psjs and a batch log

Soft proof with out-of-gamut

A proof that simulates the paper and marks where the color doesn't fit, for the designer to look at before requesting the printed proof.

Deliverable: proof sheet and tificc log

Refusing what shouldn't be converted

Another print shop's CMYK and files without a profile don't enter the batch: they become open items with a reason, for someone to decide in writing.

Deliverable: list of open items with reasons

A log that answers later

Source, profile, intent, workstation, Photoshop version and who released it. The question "what profile did this go out with?" has an answer months later.

Deliverable: registro_conversao.csv per batch

Eight arms, color that explains itself.

The same Octo cycle, applied to print color. Each arm has a narrow role; the ones who define the profile, approve the proof and release the submission are people.

Discovery
Surveys profiles and workstations

Which print shops, papers and profiles are in use, how each workstation is configured and which Photoshop version runs.
Data
Writes the color contract

Profile, intent, black point compensation and ink limit per print shop and paper, in a versioned file.
Security
Protects the source and the data

The source is never saved, a new output folder, the print shop's profile kept out of public repositories, personal metadata flagged (LGPD, Brazil's data protection law).
Architecture
Chooses the path

Recorded action, UXP script or Little CMS on the command line, depending on volume and frequency.
Development
Writes the conversion and the check

Conversion script, check script and soft proof, with the source of each rule noted.
Review
Checks by content

Mode, profile and profile class by script; a sample of values in a manual check. "It finished without errors" is not a check.
Release
Prepares the print shop folder

Checked folder and manifest. The submission is made with a person's approval.
Documentation
Records what applies to your environment

Color contract, versions, workstations and who approved each proof, with the date.

Octo converts only copies and closes the source without saving. It does not approve color, does not choose the print shop's profile and does not calibrate monitors.

Every task, its own path.

The criteria Octo uses to choose, with the documented limit of each path.

Task	Path	Notes
Convert a file now and then	Edit > Convert to Profile	Convert, never Assign, to go to CMYK
Convert a folder without a script	Recorded action + File > Automate > Batch	The profile lives inside the action, with no history
Batch with a log and refusal of what shouldn't be converted	UXP script with `convertProfile`	Photoshop 23.0 or newer, designer present
Keep an existing JSX script	ExtendScript `Document.convertProfile`	Dialogs off; legacy platform
Check the embedded profile of a folder	exiftool + Python	Read-only
Soft proof and out-of-gamut in batch	Little CMS (`tificc -p -g`)	On exported TIFF; doesn't read PSD
Convert in the cloud	Photoshop API v2	Output profile not documented in the pages read
Approve the color	The print shop's printed proof	No script replaces it

From converting by hand to a batch that explains itself.

Three steps. Each one only makes sense after the previous one has shown results on your team.

A proposal, not a promise

1 Today

Check

Octo checks the folders that already come in, without changing how you convert.

Profile and mode of each file
Missing profiles and foreign CMYK flagged
Manifest with sha256

Gain: fewer surprises on the printed proof

2 Next

Contract and script

A color contract written with the print shop and the conversion script running from it.

The source is never saved
A log of every file
Designer present and releasing

Gain: no more mistaken Assign at closing

3 Later

A proof before the proof

Soft proof with out-of-gamut flagged on every batch, before requesting the printed proof.

Proof sheet per batch
Calibrated monitor
Adjustments before the print shop

Gain: fewer printed proofs redone

Confirmed by a source.

Every point below has a source published by the vendor, by the project or by the responsible agency. The sources are in the next section.

points with a published source, each with its reference shown alongside.

ConfirmedconvertProfile in UXP since 23.0: With intent, black point compensation and dithering; colorProfileType distinguishes its own profile, the working space or none.Source: developer.adobe.com, UXP reference, Document class
Confirmedtificc proofs and flags out-of-gamut: Options -p (proofing profile), -g (flags out-of-gamut), -k (ink limit) and -e (embeds the destination profile).Source: tificc help and Little CMS source code
ConfirmedCurrent ECI profiles: PSO Coated v3, PSO Uncoated v3 (FOGRA52) and eciCMYK v2 on the downloads page; ISO Coated v2 only in the historical archive.Source: eci.org, downloads

What Octo does, and what stays with you.

Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.

Octo prepares

Surveys, calculates, organizes and produces the documents: processed files, proofs, reports and spreadsheets.

Deliverable: material ready to check

Your team checks

The client or the art director checks what Octo delivered before approving. If something doesn't add up, it goes back to Octo with the correction.

Step: checked by the person who approves

Who approves

Octo does not approve the artwork. Artwork carries no legal signature: approval of the artwork and the proof stays with the client or the art director.

Approval: client or art director

Sources.

Adobe's UXP reference and Photoshop API documentation, the 27.11 release announcement, Little CMS, ImageMagick, exiftool and ECI, consulted on Oct 31, 2026.

UXP: Document classconvertProfile, profile, mode
UXP: constantsIntent, ColorProfileType
UXP: Photoshop classgetColorProfiles
UXP: executeAsModalModal state
Photoshop APIv2; v1 ended on Jul 31, 2026
Photoshop 27.11Announcement of Oct 5, 2026
Little CMS2.19, MIT
ImageMagick, options-profile, +profile
exiftool, ICC_ProfileProfile tags
ECI, downloadsPrinting profiles

Your print color, with the right profile and logged.

The assessment starts by checking a delivery folder that already exists. You get the profile of each file, what needs a decision and the questions only your team and your print shop can answer, and you decide with that in hand.

Request an assessment