Adobe Applications & Creative Suites

Choose the Adobe App for Your Workflow

Start by choosing the Adobe application that owns the job. Compare Photoshop, Illustrator, InDesign, Premiere, After Effects, and other listed Adobe products by workflow, then check the exact version and compatibility on the product page. ProSoftStore sells specific listed product versions for a one-time payment.

Photoshop and Illustrator solve different kinds of graphic-design problems. InDesign is built around page layout rather than image editing. Premiere and After Effects often work on the same production but are not substitutes. Media Encoder processes media without replacing the editor. And several older Adobe products in the ProSoftStore catalog now belong to legacy rather than current Creative Cloud workflows.

Use this guide to match the application to your primary output and the project files it must work with.

Choose by the work you need to do

The most useful selection rule is simple:

Choose the application that owns the primary creative task, then add complementary Adobe applications only where the workflow actually requires them.

Photoshop: raster images and pixel-based composition

Choose Photoshop when pixels are the primary material.

Adobe currently positions Photoshop around image editing, compositing, graphic creation, selections, retouching, and broader raster-design workflows across desktop, web, and mobile.

Photoshop is the right starting point when you need to

• edit or retouch photographs;
• composite several images;
• remove, replace, or manipulate image content;
• create raster artwork;
• prepare visual assets for web, print, video, or other Adobe applications;
• work directly with pixel-level detail.

Look elsewhere when

the finished artwork must remain resolution-independent and scalable as vector geometry.

That is where Illustrator becomes the more natural primary environment.

Likewise, Photoshop can assemble pages, but it is not the right replacement for a multi-page publishing system such as InDesign.

Illustrator: vector graphics that need to scale

Choose Illustrator when the central asset is vector artwork.

Adobe currently describes Illustrator around logos, icons, drawings, typography, illustration, packaging graphics, and other artwork that must remain sharp across different output sizes.

Illustrator is a strong fit for

• logos and identity graphics;
• icons;
• diagrams and vector artwork;
• typography-based graphics;
• scalable illustrations;
• print and digital assets that need clean resizing;
• artwork that will later move into Photoshop, InDesign, Premiere, or After Effects.

Photoshop or Illustrator?

Use Photoshop when the work is fundamentally pixel-based.

Use Illustrator when shapes, paths, vectors, and scalability are the core of the asset.

Many creative projects use both. That does not make them interchangeable.

InDesign: page layout and publication assembly

Choose InDesign when the main job is arranging content into a designed publication.

Adobe’s current InDesign product is built for page design and layout across print and digital outputs including books, brochures, magazines, posters, eBooks, and interactive documents.

InDesign is the stronger path when you need to

• build multi-page documents;
• control typography across long publications;
• manage page structures and master-layout logic;
• combine text, images, and vector artwork;
• produce professional print or digital publication layouts.

A typical workflow may create images in Photoshop and vectors in Illustrator, then assemble those assets inside InDesign.

That is a complementary workflow rather than a reason to choose only one application.

InCopy: when writers and editors share the publishing workflow

InCopy serves a much narrower role.

Adobe currently positions InCopy around writers and editors working on text while designers continue layout work in InDesign. It supports text editing, change tracking, styling, and limited layout adjustments without forcing editorial staff to work directly in the main InDesign layout.

Choose InCopy when

• designers already use InDesign;
• writers or editors need controlled access to publication text;
• editorial and layout work happen in parallel;
• reducing document handoff conflicts matters.

Do not choose InCopy as a standalone page-design replacement

Its value depends heavily on the collaborative InDesign editorial workflow.

If the same person owns the layout and content, InDesign itself may be the more important destination.

Premiere: when editing the video is the primary job

Choose Premiere when the core task is assembling source footage into a finished video.

Adobe’s current Premiere product covers video editing, titles, effects, audio mixing, media organization, and delivery-oriented production workflows.

Premiere should usually own

• selecting and arranging shots;
• timeline editing;
• trimming;
• sequence structure;
• multiclip editorial work;
• basic titles and effects;
• editorial audio work;
• preparation of the final program.

The key distinction is editing over time.

If the primary problem is creating a sophisticated visual effect, animated graphic, tracked composite, or motion-design sequence, After Effects becomes more relevant.

After Effects: motion graphics, compositing, and VFX

Choose After Effects when the job happens inside the shot or graphic rather than primarily between shots.

After Effects remains actively developed; Adobe’s September 2026 release continues its motion-graphics, compositing, effects, color, text, and 3D-oriented production capabilities.

After Effects is a better starting point when you need to

• create motion graphics;
• animate titles and graphic elements;
• composite multiple visual layers;
• remove, replace, track, or integrate visual elements;
• create visual effects;
• build graphics that later return to a larger video edit.

Premiere or After Effects?

Premiere: edit the program.

After Effects: build or manipulate the shot, effect, or animated graphic.

Complex video production commonly needs both, but each has a different primary responsibility.

Animate: timeline-based 2D animation

Animate supports timeline-based 2D animation, frame-by-frame work, HTML5 Canvas output and established interactive animation workflows.

Animate can still make sense when

• your existing workflow depends on Animate projects;
• timeline-based 2D animation matches the job;
• HTML5 Canvas or established Animate/Flash-derived workflows are important;
• compatibility with existing assets matters more than future feature expansion.

Character Animator: performance-driven character animation

Choose Character Animator when the fastest route from a human performance to an animated 2D character is the main requirement.

Adobe currently positions Character Animator around webcam- and microphone-driven face/body tracking, automatic lip sync, puppets, performance capture, and live character animation.

It is a strong fit when

• characters are driven by live or recorded performances;
• rapid lip sync matters;
• webcam/microphone tracking is desirable;
• live streaming or fast character production is central.

It is not simply another version of Animate

Animate is timeline-oriented and supports traditional/frame-based animation workflows.

Character Animator is built around performance capture and puppeteering.

Choose according to how the animation is created.

Need help comparing animation options?

If you know animation is the right category but budget has become the main constraint, use Cheap Animation Software.

That is the approved editorial bridge for this family hub. It supports a narrower selection question without replacing the family structure.

Audition: when audio itself is the job

Choose Audition when audio production is a primary workflow rather than a small part of video editing.

Adobe continues to actively maintain Audition; the September 2026 release is version 26.5. Adobe positions it around recording, editing, mixing, restoration, podcasts, music, film, and related audio work.

Audition becomes useful when you need to

• record audio;
• edit dialogue or other source recordings;
• repair or restore problematic audio;
• mix multitrack projects;
• prepare podcast, broadcast, film, or video sound;
• move beyond the audio tools required for ordinary editorial work.

If the main job is video editing and only modest audio correction is needed, Premiere may already own the workflow.

Choose Audition when audio becomes a specialized production stage.

Media Encoder: process media without replacing the editor

Media Encoder solves a different problem again.

Adobe describes the current application around ingest, transcoding, proxy creation, batch queues, and output processing, with close integration into Premiere and After Effects. The September 2026 release remains actively developed.

Use Media Encoder when you need to

• convert media between formats;
• create proxies;
• process repeated export jobs;
• build queues;
• prepare output while other Adobe applications remain available for work;
• standardize delivery formats.

Do not choose Media Encoder as a video editor

It processes media.

It does not replace Premiere’s editorial timeline or After Effects’ compositing environment.

This distinction matters when buying software for an encoding workstation or production pipeline.

Dreamweaver: web design and front-end development

Choose Dreamweaver when the primary output is a website and you specifically want an Adobe environment for HTML, CSS, JavaScript, coding, site management, and visual web-development workflows.

Dreamweaver remains actively available and received a July 2026 update. Adobe continues to position it for web designers and front-end developers.

Dreamweaver is relevant when

• editing web code is part of everyday work;
• HTML/CSS/JavaScript are central;
• site management matters;
• a combined coding and visual-development environment suits the team.

Do not choose it because the job merely produces web graphics

If you are creating images, illustrations, banners, or design assets that another system will publish, Photoshop or Illustrator may own the creative job instead.

Dreamweaver is about constructing and managing the site itself.

Prelude: older media-ingest workflows

Prelude should be treated as a legacy destination.

Prelude may still matter when

• an established historical production pipeline depends on it;
• old projects or workstations must remain usable;
• an organization needs to access a specific legacy ingest/logging environment.

It should not be the default path for a new video workflow

For a new deployment, evaluate Premiere and Media Encoder according to the actual ingest, editorial, and transcoding requirement.

Creative Suite and Master Collection: historical creative suites

Master Collection combined multiple Creative Suite applications. Historical CS6 installations have version-specific system requirements and project-file compatibility constraints.

Consider these destinations only when you have a concrete legacy requirement

For example:

• an existing workstation must remain unchanged;
• a historical project requires an exact old Adobe environment;
• files, plug-ins, scripts, or production procedures depend on that generation;
• a project depends on that generation of applications.

What about Acrobat?

Adobe Acrobat is an approved Adobe ecosystem bridge, but it is not a structural child of this family hub.

Use Acrobat when the primary job is PDF creation, editing, document review, signing, or related document work rather than creative-media production.

Its canonical ProSoftStore placement remains outside this family because no dedicated PDF/document solution hub was validated in the approved architecture.

Six questions that usually identify the right Adobe app

1. What is the primary asset?

Start with what the user spends most of the day manipulating.

Photographic/raster pixels: Photoshop.

Vector shapes and paths: Illustrator.

Pages and publication layouts: InDesign.

Video timeline: Premiere.

Visual layers/effects over time: After Effects.

Audio waveform/multitrack audio: Audition.

Web code/site: Dreamweaver.

That question often eliminates most of the family immediately.

2. Are you creating the content or assembling it?

Illustrator and Photoshop create visual assets.

Premiere assembles video footage into sequences.

InDesign assembles text and graphics into publications.

Media Encoder processes already-created media for delivery.

Selecting by the wrong stage produces unnecessary workflow complexity.

3. Does the job require a specialist collaboration model?

A publishing team with separate designers, editors, and writers may benefit from InDesign plus InCopy.

A solo designer may not need that additional layer.

Likewise, a video team may need Premiere, After Effects, Audition, and Media Encoder together - but only because each owns a different production stage.

4. What type of animation are you making?

Motion graphics and visual compositing: After Effects.

Traditional/timeline-based 2D animation: Animate.

Performance-driven puppets and characters: Character Animator.

Do not group all three under a generic “animation software” requirement without identifying how the animation is actually produced.

5. Which other Adobe applications must exchange the project?

Creative workflows are often multi-application.

Before purchase, identify the real handoffs:

• Illustrator artwork into Photoshop or After Effects;
• Photoshop assets into InDesign;
• Premiere sequences with After Effects graphics;
• Premiere audio into Audition;
• Premiere/After Effects output through Media Encoder;
• InCopy editorial work into InDesign.

Verify exact project/version compatibility when an older release is part of the chain.

6. Are you selecting creative tools or preserving existing project files?

If a workstation or production pipeline depends on an older Creative Suite project, first verify the files, plug-ins and application versions that must remain compatible.

For a new creative workflow, compare the applications by the deliverables and production handoffs required.