Command line arguments
If it is file path then upload it, if it is URL then download it and upload it. You can use multiple paths for be able to upload multiple files in same time.
Allows ShareX to load multiple instances. By default it is not possible to open more than one instance of ShareX.
Loads ShareX in portable mode. In portable mode, the application will create a folder named “ShareX” (if it doesn’t exist already) in its startup path to save configuration files and images.
Loads ShareX to tray without showing the main window. Only if “Show tray icon” setting is enabled.
ShareX will open with default settings and won’t save any settings (ApplicationConfig.json, HotkeysConfig.json, UploadersConfig.json, History.xml) in the hard disk.
You can use any hotkey action as a command line argument.
You can find the full list of hotkey actions from
public enum HotkeyType in here.
You can execute your workflows (hotkey tasks) using their descriptions.
-workflow "Capture rectangle region & annotate"
This will execute your custom hotkey with the matching description.
This command must be used together with file or URL path. Upload will use this task setting. Only first matched task command will be used and rest will be ignored. Position of task command doesn’t matter.
"C:\ShareX.png" -task "Upload to Imgur"
After all tasks are completed ShareX will close automatically.
For example it can be used to upload two images at the same time and then close ShareX after all uploads are finished.
On startup of ShareX if hotkey registration fails then don’t show hotkey registration error window.
Specified .sxcu file path used to add custom uploader configuration to ShareX. It is also used for
.sxcu file association.
When setup is silent the wizard and the background window are not displayed but the installation progress window is.
When setup is very silent then installation progress window is also not displayed.
After setup is complete ShareX won’t run automatically.
This command makes sure that the setup will not apply initial tasks again such as creating desktop shortcut or context menu entries. It is used when ShareX updating.
This is how ShareX decides about personal path in this order:
-pCLI flag exists then use
.\Portablefile exists then use
.\PortableAppsfile exists then use
%LocalAppData%\ShareX\PersonalPath.cfgfile exists then move it to
.\PersonalPath.cfgfile exists then use file path in it.
Documents\ShareX\PersonalPath.cfgfile exists then use file path in it.
For example portable build of ShareX using 2. step there.