Short answer: reaConverter automates file conversion through three layers that share the same settings engine. The Windows context menu handles ad-hoc jobs, Watch Folders convert files the moment they land in a monitored directory, and the command-line tool (cons_rcp.exe) runs scheduled and scripted jobs. Watch Folders run as a Windows service and require local storage. The command line reads network paths without restriction. All three read the same .cfg configuration files and .act action files, so a workflow you design once in the interface runs identically everywhere. Watch Folders and the command line require reaConverter Pro.

This guide covers how those layers fit together, how to build a pipeline that survives unattended operation, and six complete workflows you can adapt.

What counts as an automated conversion workflow

A conversion workflow is automated when three conditions hold:

1. The trigger is not a person. A file arriving, a clock reaching 02:00, or another program calling an API starts the job.
2. The settings are stored, not retyped. Output format, quality, resize rules, naming, and destination live in a file, not in someone’s memory.
3. Failures are visible. The job reports what it processed, what it skipped, and why.

Most conversion setups get the first condition right and ignore the other two. That is why they break quietly. The sections below treat all three as part of the design.

The three automation layers

These layers are not alternatives so much as stages. A typical production setup uses two or three at once. A common pattern: the command line converts a historical backlog over a weekend, a Watch Folder handles new files from that point on, and the context menu stays available for one-off exceptions.

Choosing a layer

• New files arrive continuously and unpredictably → Watch Folder.
• Files arrive in known batches at known times → command line plus Windows Task Scheduler.
• A one-time archive migration → command line.
• A person decides which files to convert → context menu.
• Source files live on a network share → command line on a schedule, or reaConverter installed on the file server itself.

Configuration files: the portable unit of a workflow

Before touching automation, build the job in the reaConverter interface and save it. This is the step that makes everything else reproducible.

Configuration file (.cfg) stores conversion settings: output format and its format-specific options, destination folder, file naming rules, and post-conversion file handling. Create it with Menu → Save configuration as.

Action file (.act) stores the editing operations applied during conversion: resize, crop, rotate, watermark, color adjustments, and the rest. Create it from the Image editing tab using Save actions to file as.

The split matters. A .cfg answers “what format, where does it go, what is it called.” An .act answers “what happens to the content on the way.” Keeping them separate means you can pair one action file with several configurations, for example the same watermark and resize applied to both a WebP web output and a TIFF archive output.

Both file types load into Watch Folder setup and both can be passed to the command line:

cons_rcp.exe config.cfg actions.act -f file1.jpg file2.png file3.tiff

Practical convention: keep these files in a version-controlled folder alongside your scripts, named for the workflow rather than the format. supplier-photos-web.cfg tells a colleague more in six months than webp85.cfg does.

Layer 1: context menu conversions

Integrating reaConverter with the Windows context menu turns any selection in Explorer into a conversion job. Select files or a folder, right-click, and convert with your saved settings.

Windows 11 hides third-party entries behind Show more options, which adds a click. For staff who convert dozens of files a day, that friction is a real cost, and it is usually the point at which a Watch Folder becomes the better answer.

The context menu remains valuable as the escape hatch in an automated shop. When a file arrives outside the normal channel, someone can convert it correctly without needing access to scripts.

Layer 2: Watch Folders

A Watch Folder is an ordinary Windows folder that reaConverter monitors. Any file placed there is converted using stored settings and written wherever you specify, with no interaction.

Watch Folders run as a Windows service that uses the same conversion engine as the main application. The reaConverter window does not need to stay open, and nobody needs to be logged in. You configure a Watch Folder once through the interface, close the program, and conversions keep happening.

Watch Folders require local storage

A Watch Folder must point at a volume local to the machine running reaConverter. Network locations do not work, whether you address them as \\fileserver\incoming\ or through a mapped drive letter, because Windows does not deliver file system change notifications across SMB the way it does for local disks. A Watch Folder aimed at a share will sit there quietly and never fire.

This is a topology constraint rather than a dead end. Two ways around it:

• Install reaConverter on the machine that owns the storage. The folder is local to that server even though everyone else reaches it as a share. For engineering and document control this is usually the right answer anyway, since the files already live on a file server.
• Poll the share with a scheduled command-line job instead. cons_rcp.exe reads UNC paths without restriction. Running it on a short repeating interval reproduces most of what a Watch Folder does, at the cost of restructuring the folders into a queue. This is covered in full under Polling a network folder below.

Enabling and creating a Watch Folder

Open reaConverter, go to Menu → Watch folders, and toggle the switch ON. Click Add new folder to start the setup wizard.

Step 1: select the folder to monitor. Drag a folder onto the wizard or browse to it. Two options shape the scope:

• Read subfolders monitors the entire tree below the selected folder. Use this when incoming files are organized by project, client, or date.
• Process all files without filtering converts everything that appears. Turn it off to define file masks and exclusions on the next screen.

File masks accept both wildcards and regular expressions:

Regular expression masks are the feature that makes Watch Folders viable in engineering and document control environments, where filename structure carries meaning and only approved revisions should be processed.

There is a shortcut worth knowing: the reaConverter icon button in the bottom-left corner of the wizard loads your current conversion settings from the main interface, so you do not have to rebuild them inside the wizard.

Step 2: select where results are saved. Three options:

• Same as source folder writes converted files next to the originals. reaConverter excludes the files it creates from further processing, so this does not cause a conversion loop.
• Subfolder of source folder creates a subfolder such as Converted inside each source folder. Combined with Read subfolders, this preserves your directory structure while keeping originals and outputs separate. This is the safest default for most workflows.
• Following folder sends everything to one destination folder regardless of where it came from.

Step 3: saving settings. Choose the output format under Save files as and open the gear icon for format-specific settings such as quality and compression. Apply editing operations with Load actions file by pointing at a saved .act. Enable Create log file to generate a text record of every conversion.

Click Create Watch folder to activate it. The master switch under Menu → Watch folders stops every Watch Folder at once, which is the fastest way to halt automatic processing while you investigate something.

Turning on Create log file is not optional

For any Watch Folder that runs unattended, enable the log. A Watch Folder that silently stops processing a subset of files looks identical to one working correctly, right up until someone downstream notices a gap weeks later. The log is the only cheap way to answer “did this file get converted, and when.”

Running several Watch Folders

Create one Watch Folder per workflow rather than one folder with complex rules. A folder that resizes marketing images, a second that produces PDF issue sets, and a third that generates archive TIFFs are easier to reason about, easier to hand to a colleague, and easier to disable individually when something goes wrong.

File management after conversion

reaConverter can move or delete source files once they are processed successfully. Configure this in Menu → Saving Settings → File options before creating the Watch Folder, or include it in the .cfg you load.

Moving processed originals to an archive folder is almost always better than deleting them, and it has a second benefit: the monitored folder stays empty, so at a glance you can tell whether anything is stuck.

Layer 3: the command line

reaConverter Pro installs a command-line tool named cons_rcp.exe in the program folder. It exposes the full conversion and editing feature set through parameters, which makes it the right layer for scheduled jobs, server-side processing, and any workflow that has to be scripted.

Basic syntax

Convert a single file:

cons_rcp.exe -s "C:\input.jpg" -o "C:\output.png"

Convert a folder:

cons_rcp.exe -source_folder "C:\input\" -source_ext heic -dest_path "C:\output\" -dest_ext jpg

Convert with an editing action applied:

cons_rcp.exe -s "C:\input.jpg" -o "C:\output.webp" -resize 500x300px qh

Use saved settings instead of long parameter lists:

cons_rcp.exe config.cfg actions.act -f file1.jpg file2.png file3.tiff

Parameter rules are simple. Parameters begin with -, values follow the parameter they belong to, a parameter can take several values separated by spaces, and order does not matter. Quote any path containing spaces.

A note on line continuation. The multi-line examples below use the caret ^, which is Command Prompt and batch file syntax. In PowerShell the continuation character is the backtick ` instead. Pasting a caret-continued command into PowerShell silently runs only the first line, which looks like reaConverter ignoring your parameters.

Workflow parameters worth knowing

The full parameter list covers hundreds of format-specific options. These are the ones that shape automation behavior rather than output quality:

Two parameters turn a folder-wide command into an incremental one. -file_age restricts the job by age, so -file_age 0 converts today’s arrivals and -file_age 1 covers the last day. This is the shortest path to a nightly job that does not reprocess the whole archive, and it needs no state of your own.

Read the parameter literally: it selects by creation date, not by last modified date. For a folder that receives files, those are effectively the same thing, because Windows stamps a fresh creation time on a file copied or moved into a new location. For a folder where files are edited in place, they are not the same thing at all, and -file_age will not see yesterday’s edit to a file created last year.

-use_file_list is the more general tool. A script decides which files qualify, writes their full paths to a plain text file, and reaConverter converts exactly those. Any rule you can express in PowerShell becomes a conversion filter, which matters when age alone is not the right test.

Two further mechanisms cover the rest. -overwrite 0 skips any file whose output already exists, so rerunning a job over a large folder only fills the gaps. -move_files empties the source folder as it succeeds, so whatever remains is by definition unprocessed.

Silent execution and logging

Suppress the window for scheduled tasks:

cons_rcp.exe [parameters] /hide

Capture output to a log file with standard redirection:

cons_rcp.exe "C:\config.cfg" "C:\actions.act" > "C:\logs\nightly.txt"

Append rather than overwrite with >> if you want a running history. Rotate these logs, or a busy pipeline will produce a file nobody can open.

Return codes

cons_rcp.exe sets an exit code that your script should check:

Code 8 is the one that matters most in production. It means the job ran and partially succeeded, which is exactly the failure mode that goes unnoticed without explicit handling.

A minimal batch wrapper:

@echo off
setlocal
set LOG=C:\logs\convert_%date:~-4%%date:~3,2%%date:~0,2%.txt

"C:\Program Files\reaConverter\cons_rcp.exe" ^
  -source_folder "D:\incoming\" -source_ext tif -file_age 0 ^
  -dest_path "D:\published\" -dest_ext pdf ^
  -move_unprocessed_files 1 -move_unprocessed_files_folder "D:\quarantine\" ^
  /hide >> "%LOG%" 2>&1

if %ERRORLEVEL% EQU 0 exit /b 0
if %ERRORLEVEL% EQU 8 (
  echo PARTIAL FAILURE, check quarantine >> "%LOG%"
  powershell -Command "Send-MailMessage -To 'ops@example.com' -Subject 'Conversion partial failure' -Body 'See %LOG%' -SmtpServer 'smtp.example.com' -From 'jobs@example.com'"
  exit /b 8
)
echo FAILED with code %ERRORLEVEL% >> "%LOG%"
exit /b %ERRORLEVEL%

Scheduling with Windows Task Scheduler

Four settings decide whether a scheduled conversion job works reliably:

1. Run whether user is logged on or not. Otherwise the task waits for a session that may never exist on a server.
2. A service account with explicit permissions on the source, destination, quarantine, and log folders. Most first-run failures on scheduled conversion tasks are permission failures, not conversion failures.
3. UNC paths, not mapped drives. Mapped drive letters belong to interactive sessions and will not exist for a task running without one. Write \\fileserver\projects\incoming\ rather than P:\incoming\. This applies to command-line jobs, which handle network paths fine. Watch Folders are the opposite case and need local storage.
4. Start in set to the folder containing your script, so relative paths behave.

Polling a network folder

Watch Folders cannot monitor a share, but a scheduled command-line job can poll one. Run cons_rcp.exe against the share on a short repeating interval and you get the same outcome by a different route: files converted shortly after they arrive, with no one watching.

The trade is that the folder stops being a location and becomes a queue. A Watch Folder tracks which files it has already seen. A polling job has no memory, so every run would reconvert everything unless processed files leave. Moving them out is what supplies the state:

cons_rcp.exe -source_folder "\\fileserver\incoming\" -source_ext tif ^
  -dest_path "\\fileserver\converted\" -dest_ext pdf ^
  -move_files 1 -move_files_folder "\\fileserver\done\" ^
  -move_unprocessed_files 1 -move_unprocessed_files_folder "\\fileserver\failed\" ^
  /hide

One folder becomes four: incoming, converted, done, failed. Incoming is empty whenever the queue is caught up, which is a genuinely better operational signal than anything a Watch Folder gives you.

Four settings make the difference between this working and this hurting:

Do not start a new instance. In the task’s Settings tab, set the behavior for an already-running task to Do not start a new instance. Without it, a run that takes longer than the interval overlaps with the next one and two processes fight over the same files.

Quarantine is mandatory, not optional. In a nightly job, a file that always fails wastes one attempt per day. In a job polling every minute, it fails 1440 times a day, and each attempt reopens it across the network. -move_unprocessed_files is what turns a poison file from a hot loop into a single entry in a folder someone checks.

Partial copies get much more likely. A large file arriving over the network exists in the folder before the copy finishes, and a fast poll will find it mid-write. Have the sender write to a staging folder on the same share and rename into the queue, since a rename within a volume is atomic. If you cannot control the sender, -file_size_more and -check_files reduce the damage but do not eliminate it.

The floor is one minute. Task Scheduler’s repetition interval bottoms out at one minute in the interface, with a duration of Indefinitely. That is fast enough for nearly every workflow. If you genuinely need seconds, do not fight the scheduler: write a small loop script that sleeps and calls cons_rcp.exe, and register that as a single task triggered at startup.

Expect return code 7, no files to convert, on most runs. It means the queue was empty, which is the normal state. Treat 7 as success in any alerting you build, or you will alert constantly.

Six workflows you can adapt

Each of these follows the same template: what triggers it, what it produces, and how it is configured.

1. Nightly DWG issue sets for document control

Situation. An engineering team saves drawings throughout the day. Document control needs a PDF of every drawing revised that day, delivered to a review folder each morning, without an AutoCAD seat on the server.

Trigger. Windows Task Scheduler at 02:00. The drawings live on a share, so this is a command-line job rather than a Watch Folder.

Produces. One dated folder of PDFs per night, mirroring the project directory structure.

Command. PowerShell, because selecting yesterday’s revisions is a filtering problem before it is a conversion problem:

$stamp = Get-Date -Format "yyyy-MM-dd"
$list  = "C:\jobs\dwg_today.lst"

Get-ChildItem "\\eng\projects\" -Recurse -Filter *.dwg |
  Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-1) } |
  Select-Object -ExpandProperty FullName |
  Set-Content -Encoding ASCII $list

& "C:\Program Files\reaConverter\cons_rcp.exe" `
  -use_file_list $list `
  -dest_path "\\eng\review\$stamp\" -dest_ext pdf `
  -dxf_dwg_layout 1 -pdf_paper 12 `
  -save_path 1 -save_path_option 1 `
  -move_unprocessed_files 1 -move_unprocessed_files_folder "\\eng\review\_failed\" `
  /hide *>> "\\eng\logs\dwg_nightly.txt"

Notes. Filtering on LastWriteTime is the point. Document control asks for drawings revised yesterday, and a drawing revised yesterday was very likely created two years ago, so any rule based on creation date misses exactly the files that matter. Build the format date string yourself rather than using %DATE%, whose output contains slashes on most locales and is not a legal path component. -dxf_dwg_layout 1 outputs model space only, which is usually what reviewers want. -save_path 1 reproduces the project folder structure inside the dated review folder, so reviewers navigate a layout they already know.

Why not -file_age. -file_age 1 is a much shorter way to say “recent”, and for most incoming-folder workflows it is the right tool. It does not fit here because it selects on creation date, and drawings under revision are edited in place: the file was created when the project started and only its modified date moves. There is a second, less obvious reason. NTFS carries the original creation timestamp forward when an application saves by writing a temporary file and renaming it over the original, which is exactly how many CAD and office applications write. Even a save that replaces the file wholesale can keep the old creation date.

If drawings instead arrive in the folder as fresh copies from elsewhere, the constraint disappears and the whole script collapses to -source_folder "\\\\eng\\projects\\" -source_ext dwg -read_subfolders 1 -file_age 1.

2. CAD handoff for CNC and non-Autodesk partners

Situation. Partners and fabrication shops need DXF. Designers work in DWG. Nobody wants to remember to export.

Trigger. Watch Folder on D:\shares\handoff\, a local path on the file server, which designers reach as \\eng\handoff\. reaConverter is installed on the server itself, because a Watch Folder cannot monitor a share from another machine. A regex mask means only released revisions convert:

/[A-Z]{4} \d{4}_Rev[A-Z]\.dwg/

Configuration. Output DXF with -dxf_version 4 for AutoCAD 2000 compatibility, which most CNC software reads without complaint. Set -dxf_text 0 to convert text to polygons if the receiving system renders fonts inconsistently, or -dxf_text 1 to keep text editable. Confirm which the partner needs before standardizing.

Notes. The regex mask is what makes this safe. Without it, every working file dropped in the folder becomes a handoff document, and partners end up cutting parts from unreleased geometry.

3. Prepress normalization for a print queue

Situation. Client artwork arrives as RGB JPEG, PDF, AI, and PSD. The RIP wants CMYK TIFF at 300 dpi with a known ICC profile.

Trigger. Scheduled every 15 minutes, or a Watch Folder if P:\ is a local volume on the prepress machine rather than a share.

Produces. RIP-ready CMYK TIFFs, with originals archived and problem files quarantined.

Command.

cons_rcp.exe -source_folder "P:\artwork_in\" ^
  -dest_path "P:\rip_queue\" -dest_ext tif ^
  -tif_save_in_cmyk 1 -tif_compression 7 ^
  -dpi_option 2 -dpi_x 300 -dpi_y 300 ^
  -icc_option 3 -icc_file "C:\profiles\ISOcoated_v2.icc" ^
  -adobe_res 300 -adobe_color_res 32 -adobe_aa 1 ^
  -move_files 1 -move_files_folder "P:\artwork_archive\" ^
  -move_unprocessed_files 1 -move_unprocessed_files_folder "P:\artwork_problem\" /hide

Notes. -icc_option 3 assigns the profile, -adobe_res 300 controls the rasterization resolution when reading PDF and AI sources, and -adobe_color_res 32 reads them as CMYK directly. Splitting outputs into an archive folder and a problem folder means the operator’s morning check is a single glance at whether artwork_problem is empty.

4. Scanned document archive to searchable PDF/A

Situation. A backlog of scanned TIFFs from a document imaging project needs to become searchable, standards-compliant PDF/A for long-term retention.

Command.

cons_rcp.exe -source_folder "E:\scans\" -source_ext tif -read_subfolders 1 ^
  -dest_path "E:\archive\" -dest_ext pdf ^
  -create_searchable_pdf 1 -searchable_pdf_lang eng ^
  -create_pdf_a 1 -create_linearized_pdf 1 ^
  -skip_blank 1 -skip_blank_accuracy 95 ^
  -save_path 1 -save_path_option 1 ^
  -auto_rotate d -remove_bw_noise 2 b ^
  -check_files 1 /hide > "E:\logs\archive_run.txt"

Notes. -auto_rotate d deskews pages, which measurably improves OCR accuracy on scans fed through a sheet feeder. -remove_bw_noise clears speckle before OCR runs. -skip_blank removes the empty backs of single-sided originals scanned in duplex mode. Run a 200-file sample first and check the text layer before committing the full archive.

5. Multi-frame DICOM to shareable PDF

Situation. A clinic needs to send imaging studies to referring physicians who have no DICOM viewer. Each study should become one PDF containing every frame.

Trigger. Watch Folder on a study export directory, or a command-line job invoked by the export tool.

Command.

cons_rcp.exe -source_folder "D:\dicom_export\" -source_ext dcm ^
  -dest_path "D:\referral_pdf\" -dest_ext pdf ^
  -multipage_option 1 -multipage_loading_option 0 ^
  -pdf_compression 6 -pdf_paper 12 ^
  -change_to_gray24 /hide

Notes. -multipage_loading_option 0 reads every frame rather than only the first. -multipage_option 1 keeps each study as its own PDF instead of merging studies together. -pdf_paper 12 uses the original image dimensions, which avoids the letterboxing that fixed paper sizes introduce on non-standard aspect ratios.

This workflow handles format conversion only. Anything involving patient identifiers, retention, or transmission belongs to your clinical information governance process, not to a conversion tool.

6. Supplier photos to web-ready assets

Situation. Suppliers send product photography in whatever their camera or phone produced: JPEG, HEIC, TIFF, occasionally PSD. The web team needs consistent WebP at a fixed maximum dimension, plus thumbnails, plus the originals kept for reprocessing.

Trigger. Watch Folder on D:\marketing\incoming\, local to the machine running reaConverter and published to suppliers as a share. Read subfolders enabled so each supplier keeps their own subfolder.

Produces. A web subfolder beside each supplier’s originals, containing the WebP asset and its thumbnail.

Configuration. Output to Subfolder of source folder named web. Format WebP, quality tuned for your image type. Action file applies -resize 1600x0px qh to cap width while preserving proportions, and -auto_rotate exif so phone photos land right way up. -create_thumbnails 1 with -thumbnails_width 300 produces the listing thumbnails in the same pass. Originals move to an archive folder after processing.

Notes. Generating the thumbnail in the same pass rather than a second job removes an entire class of desynchronization bug, where a product has a full-size image but no thumbnail because the second job failed.

Designing a pipeline that survives unattended operation

The conversion itself is rarely what breaks. These are.

Partially written files. A large file copied over a network appears in the folder before the copy finishes. Have the sending process write to a staging folder on the same volume and then rename or move into the watched folder, since a move within a volume is atomic. If you cannot control the sender, run a scheduled command-line job instead of watching in real time, where -file_age and -file_size_more let you pick up files only after they have settled.

Feedback loops. Writing output into the folder being watched is the classic mistake. reaConverter excludes files it created when you use Same as source folder, but if a separate tool writes into that folder, or if you convert to a format that is also an input format for the same Watch Folder, you can still build a loop. The Subfolder of source folder option avoids the whole category.

Silent partial failures. A run that converts 998 of 1000 files returns code 8 and looks fine in a log nobody reads. Combine -move_unprocessed_files with a quarantine folder and check whether that folder is empty. An empty folder is a much clearer signal than a log line.

Name collisions. Different source formats converging on one output format collide: drawing.dwg and drawing.dxf both become drawing.pdf. Decide explicitly with -overwrite, and use -file_name_mask_suffix to disambiguate when both outputs must survive.

Permissions. Scheduled tasks run as a service account. That account needs read on the source, write on the destination, write on quarantine, and write on the log path. Test by running the exact command as that account before scheduling it.

Idempotency. Ask what happens if the same file is processed twice. In most workflows the answer should be “the same output, overwritten harmlessly.” If reprocessing produces duplicates or double-applied watermarks, redesign before going live rather than after.

Capacity planning

Conversion throughput varies by orders of magnitude across formats. A 2 MB JPEG resize and a 40 MB DWG raster render are not comparable operations, and no general number is useful.

Measure instead. Take 100 files representative of your real input mix, time a single run, and extrapolate. Then apply these adjustments:

• Network storage is frequently the bottleneck rather than the CPU. If sources sit on a share, test with local copies to see how much of your runtime is transfer.
• -temp_folder pointed at a local SSD helps significantly for formats that stage large intermediate data, particularly PDF, PSD, and large CAD files.
• -cpu_usage lets a background job coexist with interactive work. Set -cpu_usage 1 for jobs running during business hours and 3 for overnight windows.
• Splitting by subfolder across several parallel invocations scales better than one process for very large backlogs, provided your storage keeps up.

For a large historical migration, run the backlog once from the command line and set up a Watch Folder for the ongoing stream. Trying to push a 50,000-file backlog through a Watch Folder works, but it gives you no progress visibility and no easy way to pause.

Frequently asked questions

Can reaConverter run conversions on a Windows Server without a logged-in user? Yes. Use the command-line tool with the /hide parameter and schedule it through Windows Task Scheduler with “Run whether user is logged on or not” enabled. Grant the service account permissions on all source, destination, and log paths, and use UNC paths rather than mapped drive letters.

Does automated conversion require an internet connection? No. reaConverter processes files locally on your machine. Files never leave your hardware, which is what makes it usable for medical imaging, engineering drawings, and other material that cannot be uploaded to a web service.

Which reaConverter edition includes automation features? Watch Folders and the command-line tool are reaConverter Pro features. Context menu integration is available more broadly.

How do I convert only files added or changed since the last run? Four approaches, in increasing order of control. -file_age is the simplest: -file_age 0 selects files created today and -file_age 1 covers the last day. -overwrite 0 skips any file whose output already exists, which makes a rerun over a whole folder fill only the gaps. -move_files empties the source folder as conversions succeed, so anything left is unprocessed by definition. When age is not the right test, have a script write the qualifying paths to a text file and pass it with -use_file_list. The usual reason is that -file_age measures creation date, so files edited in place keep their original timestamp and stay invisible to it.

Can one Watch Folder produce two different outputs from the same file? Not in a single Watch Folder. Create a second Watch Folder pointing at the same source directory with different saving settings, or use a command-line job with two invocations. The thumbnail parameters are an exception: -create_thumbnails through -create_thumbnails_5 generate up to five additional sized outputs in the same pass.

What happens if a file fails to convert? The job continues with the remaining files and returns exit code 8 to indicate that not everything was converted. Set -move_unprocessed_files 1 with a quarantine folder so failed files are separated for review rather than left in place where they will be retried indefinitely.

Can a Watch Folder monitor a network share? No. Watch Folders require storage local to the machine running reaConverter, because Windows does not deliver file system change notifications across SMB. Two workarounds: install reaConverter on the server that owns the storage, so the folder is local to it, or poll the share with a scheduled cons_rcp.exe job using -move_files to move processed files out of the queue.

Can I apply different settings to different file types in one folder? Yes, by creating several Watch Folders on the same directory with different file masks, or by running several command-line invocations with different -source_ext values. Masks accept regular expressions, so filename conventions can drive routing.

Does reaConverter preserve metadata during automated conversion? Use -copy_exif 1 and -copy_iptc 1 to carry EXIF and IPTC data to the output, and -icc_option 2 to retain the ICC profile. -same_date 1 keeps the original file timestamp on the converted file, which matters for archive workflows where the file date is the record date.

Where to go next

Build your first automated workflow in this order:

1. Configure the conversion in the reaConverter interface and verify the output on a handful of real files.
2. Save it as a .cfg, and save any editing operations as an .act.
3. Choose your trigger: a Watch Folder for continuous arrivals, a scheduled command-line job for batches.
4. Add a quarantine folder and enable logging before the job goes live rather than after the first incident.
5. Run it against a copy of real data for a week before pointing it at production directories.

Related guides in this knowledge base cover Watch Folders, command-line usage, and automation in more depth. Full parameter references are available for the command-line interface, Watch Folders, and configuration and action files.

If you are a software developer who is trying to design a program that, among others, can deliver PDF conversion, reaConverter Pro is just what you need. Through its advanced feature that allows it to be operated through the command-line interface, reaConverter will easily integrate into the custom solution that meets the needs of your program’s client.

Command-line

reaConverter Pro is designed precisely for developers, professional image designers and other types of advanced users. Apart from its GUI interface, this software can be operated through command-line. Or in other words, it can receive commands written as text lines, which dictate it to undertake specific operations. This feature is mainly intended for programming, so it was developed for robots, not for humans. Compared to a GUI (graphical user) interface, where you mainly operate your computer using the mouse, the command-line is more difficult to use, because it requires users to have thorough knowledge of how to send commands to command prompt. However, this feature is a lot more effective when you need to do a complex set of tasks related, for example, with processing a large number of images. Or with converting PDFs.

PDF

The PDF or Portable Document Format is considered to be one of the “safest” and most convenient formats for multi-page text documents. However, it has the disadvantage of needing a special application or a plug-in installed on your digital device, which might not always be easy to find and might take long loading times. With reaConverter, transforming your PDFs into more accessible image formats such as JPEG, PNG or TIFF — can quickly become part of a custom programming solution used by developers. For users who have to deal with reoccurring conversions of PDFs, with documents stored on several computers or with including a series of image editing operations as part of the conversion process, reaConverter can be part of an effective custom solution.

Install reaConverter Pro

Using reaConvert through command-line will increase the speed of handling the conversion of your PDFs, generating an increase in your productivity and the chance to handle your files more securely, with less errors and less computer resources used.

Through its command-line tool, cons_rcp.exe, reaConverter facilitates the processing of over 550 files formats, including conversion from and into PDF.

How does it work?

The tool can be used directly from the command-prompt, Windows batch command files or through third party applications, you use can settings from reaConverter’s .cgf (configuration) and .act (action) files.

Here is a basic usage example. To convert one PDF file to .jpg run from cmd:

cons_rcp.exe -s "C:\Path_to\source_file.pdf" -o "C:\Path_to\output_file.jpg"

That’s all!

reaConverter will take source_file.pdf and convert it into output_file.jpg.

In the former type of files you can set the output format or what you wish your PDF file to be converted in, and in the latter you can set the specific processes you want to apply to your files. For a complete guide to using command-line in order to integrate reaConverter Pro as part of your custom solution, as well as a full list of required and optional parameters you can check Command Line Interface Reference Guide

RAW image conversion represents a key feature used by professional photographers, graphic artists, web designers and other types of advanced image editors. In case you are a developer who designs a program addressed to these users and which can deliver RAW conversion, together with a wide array of image editing options, reaConverter Pro is just what you need! Why? Because, as opposed to many other converters, reaConverter Pro not only supports a GUI interface, but can also be operated through command-line. Which means it can help you integrate a large variety of image conversions — including from the RAW format — in your very own custom solution.

RAW image files, also known as digital negatives, store image details with a high degree of accuracy. Most professional photographers prefer to set their cameras in the RAW shooting mode because this means the lens will capture images that are as close as they can get to what you can see with your naked one. Moreover, RAW image files are preferred by professionals because they allow a wide range of computer processing. In other words, they provide more control for the photographer on aspects such as contrast and saturation, applying color filters and correcting the white balance.

However, in addition to all these advantages, RAW images also have an important drawback: they tend to be huge! One RAW file can get up to 6 times larger than a JPEG, which means RAWs are more difficult to send by e-mail and they take a lot of space on your computer. In addition, they are not compatible with most regular image viewers and can often be opened and edited only using an advanced graphics editing program, such as Corel Draw or Adobe Photoshop.

reaConverter Pro provides a quick and easy way to convert RAW images and apply a wide-ranging set of image editing options, which you can include in your own integrated solution. A program of this kind will help its user automate the reoccurring operations related to handling their RAW files, thus spending less time repeating the same operations, and generally increasing productivity and being more effective.

Install reaConverter

How does it work?

Through reaConverter’s command-line tool, cons_rcp.exe. Over 500 image formats can be processed and converted through this tool, including digital camera RAW images. The tool can be accessed directly from the command-line interface.

The tool allows you to set the output format of the RAW file — several accessible formats are available, such as JPG, PNG or TIF.

To convert one CR2 raw file run from cmd:

cons_rcp.exe -s "C:\Path_to\input_file.cr2" -o "C:\Path_to\output_file.jpg"

You can use config.cfg and action .act files for batch raw conversion and editing:

cons_rcp.exe "C:\Path_to\cfg_file.cfg" "C:\Path_to\act_file.act" -f source_file1 source_file2 source_file3

Configuration (.cfg) and action (.act) files are useful to automate the image conversion and editing process, especially when dealing with large numbers of images.

Configuration files contain details about the output extension of the converted images and the destination folder, as well as other additional features, such as RAW Formats Loading Settings, file name modifications or other conversion options.

Action files include the actual editing actions that will be applied to images, such as resizing, cropping, rotating, adjusting white balance, watermarking, etc.

The .cfg and .act files can be created using any text editor, but it is easier to create them using directly reaConverter.

Any parameter from .cfg or .act file can be specified in a command line, for example

cons_rcp.exe -s "C:\Path_to\input_file.cr2" -o "C:\Path_to\output_file.jpg" -resize 50x50% qh 1 -jpg_quality 100

You can specify the exact processes you want to apply to your files, involving image editing. A complete set of instructions on how to use reaConverter Pro to integrate RAW command-line image conversion in your own custom solution, including a list of parameters, is available in our (CLI) Command Line Interface Reference Guide.

You are welcome to contact our technical support when you have any questions about reaConverter.

Are you designing a program targeting people who work in architecture, construction engineering or design? If so, you probably want to add DWG conversion as one of its useful features. DWG (“Drawing”) is one of the most helpful and popular formats in handling computer-aided design or drafting (CAD).

However, though preferred by many for its ability to edit and optimize 3D design data and metadata, DWG files also have a few drawbacks. Firstly, in order to open them you need to have AutoCAD or IntelliCAD installed, and using these programs requires not only a powerful computer, but also special training. Secondly, DWG files tend to have very large sizes and require long loading times. For all these reasons, most people who work with DWGs prefer to be able to convert them into PDFs, because thus it becomes much easier to store, open and e-mail them.

If you are a developer who wants to integrate DWG conversion into a customized solution, reaConverter Pro is precisely what you need. This easy-to-install software which can be downloaded at reaconverter.com and has a 15-day free trial period.

Install reaConverter

reaConverter can be operated both through a GUI interface and through command-line. In order words, you can work with reaConverter not only by issuing command through graphic interface, but also by writing “command lines”. The latter option is particularly useful when you want to include DWG conversion as a feature in the software you are designing. Command-line is an effective way to automate reoccurring conversion operations and generally simplify the way users handle image manipulation. It also increases the operation speed, thus saving time and energy, and decreases the possibility of errors.

reaConverter Pro supports conversion and image editing through command-line for over 500 image file formats, including DWG.

How does it work?

Directly from the command-line, through command (batch) files or through third party applications.
In each case, you can use reaConverter’s command-line tool, cons_rcp.exe, which allows you run conversion with configuration (.cfg) and action (.act) files.

Here is the simple usage of cons_rcp.exe:

cons_rcp.exe -s source_file -o output_file [cfg_file.cfg] [act_file.act]

In the config files, you can set the output format of the converted file, as well as where you want to save it on your computer, under what name, and using what kind of conversion options. In the action type of files, you can define the exact image editing actions you want to apply to the images. You can read more about config and action files here: reaconverter.com/features/config-and-action-files.html

Detailed information about how to use command-line for converting DWG files, together with a list of required and optional parameters for doing conversions through command-line, is available at reaconverter.com/features/command-line.html

Moreover, if you encounter any difficulties integrating DWG conversion in your customized software, reaConverter also offers hight quality technical support.

The TIF (Tagged Image File) format is often preferred by photographers because of the image quality it provides, as well as its compression features and availability for editing. TIFs provide high colour-depth images and smaller processing times than, for example, EPS or AI files. Apart from photography, the TIF format is also used in the professional printing or publishing industry and in graphic art.

As opposed to JPEGs, which provide a “lossy compression” of the image, TIF files can ensure a “lossless” compression, thus retaining all the image details with increased accuracy. This, however, also means that uncompressed TIF files tend to get very large and are more difficult to store or share.

With its equal range of both advantages and disadvantages, the TIF format is preferred by some and avoided by others. If you are a developer who plans to create an integrated solution that offers its users the possibility to convert image files both to and from the TIF format, here are 3 essential tips:

1. Choose a professional converter which can be easily incorporated in the custom solution you plan to design. reaConverter Pro is a great option, because apart from its GUI interface, it can also be operated through the command-line interface. This means that you can run it both directly, by issuing command through mouse clicks, or indirectly, by writing ”command lines” which dictate the program what operations to undertake. The first option might seem easier at first glance, but it is less effective when you plan to do advanced programming. In fact, reaConverter Pro is precisely addressed to developers and professional image designers, and it can be tried for free at reaconverter.com

 

2. Use reaConverter Pro to automate a series of routine and/or reoccurring operations connected to how your software handles conversions to and from the TIF format. Thus, you will be able to increase your productivity, spend less time doing tedious operations over and over again, as well as avoid errors and generally work more effectively.

 

3. Use the program’s command-line tool, cons_rcp.exe, to integrate the conversion of TIFs in and from a large variety of formats, including JPG, PNG, PDF and many others — in your custom programming solution. The tool can be used through third party applications via command-line interface. By using it, you can also define the variety of image editing actions to apply to your files. Depending on what you plan to do with your TIF files, reaConverter lets you choose between 2 kinds of CCIT compression: Group 3 compression and Group 4 compression. A comprehensive command-line interface manual is available at this address: http://www.reaconverter.com/features/command-line.html

Example of command-line conversion:

Here is a quick tutorial of how you can find it and how you can start using the command-line feature.

To convert TIF file into JPG try:

cons_rcp.exe -s "C:\source_file.tif" -o "C:\output_file.jpg" -jpg_quality 100%

Batch TIF to JPG conversion from one folder to another:

cons_rcp.exe -source_folder "C:\source_folder\" -source_ext tif -dest_path "C:\output_folder\" -dest_ext jpg

Command-line tiff conversion tool is an advanced feature meant for professional use, and is available in Pro edition only.

• (CLI) Command Line Interface Reference Guide

   Download and try reaConverter Pro   

“I am looking for a tool to open EPS images from a webpage and save them as JPEGs to another location. Can reaConverter help me do this?”

One of our users recently sent us this question, so we passed it on to Alexander Korostelev from reaConverter, together with a few other questions regarding the use of a converter through a command-line interface.

Here is the interview that resulted:

Q: Can you run ReaConverter through a command-line interface in order to convert EPS images?

A: Yes, any advanced user can run ReaConverter from his application or webpage using the command-line interface. Running through command-line is an advanced feature available with ReaConverter Pro – a piece of software intended mainly for developers, image designers or other types of users who do image processing professionally. Command-line is usually preferred by advanced computer users because it allows them to have more control over a program or an operating system. Using command-line basically means writing lines of text or “command lines” which instruct the computer program to undertake certain processes. This is slightly more difficult than issuing commands using your mouse, as one does on a GUI (graphical user interface) operating system, so this is why we recommend using command-line only for advanced users.

Q: Why use the command-line feature?

A: Because you save a lot of time and generally increase your productivity. Command-line allows you to write commands that help you automate and manage more efficiently a whole range of reoccurring operations related to applying digital editing to your images. It also makes your job a lot easier if you have images stored on several computers. It is certainly the best option for the advanced user who plans to convert EPS images from a webpage and wants to have the output files saved in a different location. Generally speaking, using the command-line interface allows you to work faster, reduce errors and handle images more easily.

Q: How do you use the command-line feature to convert an EPS image?

A: Firstly, you need to download and install ReaConverter Pro, which can be tried for free at reaconverter.com. This program supports command-line conversion and image processing for over 400 image formats, including Encapsulated PostScript or EPS files. Secondly, you will use ReaConverter’s command-line tool, cons_rcp.exe, which will allow you to do conversions and image editing either from the command-line, command (batch) files or by using third party applications. A comprehensive list of instructions about how to use this tool, together with a list of parameters, is available here.

Download and try reaConverter  (~30 MiB)

You are welcome to contact our technical support when you have any questions about reaConverter.