ImageObject and HowTo Describe Fundamentally Different Content
ImageObject describes a single visual asset: one photo, one diagram, one image. HowTo schema describes a multi-step process: a named sequence of instructions, each with its own name, text, and optional supporting image. They are not competing ways to mark up the same content. They apply to entirely different content shapes, and most confusion between them comes from the fact that HowTo steps frequently contain images, which is exactly where the two types meet.
How HowTo Schema Structures Step-by-Step Content
A HowTo block declares a name, an overall description, and a step array. Each entry in that array is a HowToStep with its own name and text, and optionally its own image and url pointing to an anchor within the page. HowTo can also declare totalTime, supply (materials needed), and tool (equipment needed), none of which have any equivalent in ImageObject.
The HowToStep array is ordered, and that order carries meaning. Google's rich result rendering for HowTo content displays steps in the sequence declared in the schema, not necessarily the visual order on the page, so the two need to match. Getting the step order wrong is a common source of a HowTo rich result that looks correct in the validator but reads confusingly once it renders in search.
Where ImageObject Nests Inside HowTo
This is the actual overlap point, and it is not a conflict. When a HowToStep includes an image property, the value can be a bare URL, but a full ImageObject with caption and dimensions gives that step's supporting photo the same citation-readiness any other image on the page would get. A well-marked-up assembly guide or usage tutorial uses HowTo for the process and ImageObject for every step's visual, nested one inside the other.
The same pattern extends to the HowTo's own top-level image property, separate from any individual step's image, which represents the process as a whole rather than one specific step. That top-level image also benefits from a full ImageObject rather than a bare URL, for the same reason a BlogPosting's featured image does.
When Each Applies to Ecommerce Content
A product assembly guide, a sizing tutorial, or an installation walkthrough is HowTo territory: the content is fundamentally a sequence, and HowTo schema is the primary type. A single product photo, a comparison chart, or a standalone diagram inside an article that is not part of a numbered sequence is ImageObject territory on its own, with no HowTo wrapper needed. See the 12 diagram types for ecommerce SEO for where each pattern shows up most often.
Some ecommerce content sits in between: a "how to choose the right size" guide might be built around a comparison chart rather than a numbered sequence. In that case, ImageObject on the chart is the right primary treatment, and HowTo schema would be a poor fit even though the content is instructional in spirit.
Key Differences at a Glance
HowTo is process-shaped: ordered, sequential, built around a start and an end. ImageObject is asset-shaped: a single, self-contained description with no notion of sequence. HowTo can exist without any images at all, though rich results favor steps that include them. ImageObject can exist entirely independent of any process, describing a single photo on a page that has no instructions at all.
HowTo schema also carries fields with no image equivalent at all, such as totalTime and supply, while ImageObject carries fields with no HowTo equivalent, such as license and creator. The two vocabularies overlap only at the single point where a step or the overall process references an image.
Actionable Takeaway
If your content is a numbered sequence of actions, mark it up with HowTo first, then add a full ImageObject to every step that has a supporting photo or diagram rather than leaving those images as bare URLs. See how to add ImageObject schema to an image for the property-by-property walkthrough that applies whether the image sits inside a HowTo step or stands entirely on its own.
Audit existing HowTo content on your site specifically for this gap. It is common for a HowTo block to validate cleanly while every step image is still a bare URL, which means the process is well described but its supporting visuals are not individually citable.