-help  Prints a short usage notice to stderr.

-listen
       Make the viewer listen on port 5500+display for reverse connections from a server. WinVNC supports
       reverse connections using the "Add New Client" menu option, or the -connect command  line  option.
       Xvnc requires the use of the helper program vncconnect.

-via gateway
       Automatically create encrypted TCP tunnel to the gateway machine before connection, connect to the
       host through that tunnel (TightVNC-specific). By default,  this  option  invokes  SSH  local  port
       forwarding,  assuming that SSH client binary can be accessed as /usr/bin/ssh. Note that when using
       the -via option, the host machine name should be specified as known to the gateway  machine,  e.g.
       "localhost" denotes the gateway, not the machine where vncviewer was launched. See the ENVIRONMENT
       section below for the information on configuring the -via option.

-shared
       When connecting, specify that a shared connection is requested. In TightVNC, this is  the  default
       mode, allowing you to share the desktop with other clients already using it.

-noshared
       When  connecting,  specify  that the session may not be shared. This would either disconnect other
       connected clients or refuse your connection, depending on the server configuration.

-viewonly
       Disable transfer of mouse and keyboard events from the client to the server.

-fullscreen
       Start in full-screen mode. Please be aware that operating in full-screen mode may confuse X window
       managers.  Typically,  such  conflicts  cause incorrect handling of input focus or make the viewer
       window disappear mysteriously. See the grabKeyboard setting in the RESOURCES section below  for  a
       method to solve input focus problem.

-noraiseonbeep
       By  default,  the  viewer  shows  and  raises  its window on remote beep (bell) event. This option
       disables such behaviour (TightVNC-specific).

-user username
       User name for Unix login authentication. Default is to use current Unix user name. If this  option
       was given, the viewer will prefer Unix login authentication over the standard VNC authentication.

-passwd passwd-file
       File  from  which  to  get  the  password  (as generated by the vncpasswd(1) program). This option
       affects only the standard VNC authentication.

-encodings encoding-list
       TightVNC supports several different compression methods to  encode  screen  updates;  this  option
       specifies  a  set  of  them  to use in order of preference. Encodings are specified separated with
       spaces, and must thus be enclosed in quotes if more than one is specified. Available encodings, in
       default  order  for  a  remote  connection, are "copyrect tight hextile zlib corre rre raw". For a
       local connection (to the same machine), the default order to try is "raw  copyrect  tight  hextile
       zlib  corre rre". Raw encoding is always assumed as a last option if no other encoding can be used
       for some reason. For more information on encodings, see the section ENCODINGS below.

-bgr233
       Always use the BGR233 format to encode pixel data. This reduces network traffic, but colors may be
       represented  inaccurately.  The bgr233 format is an 8-bit "true color" format, with 2 bits blue, 3
       bits green, and 3 bits red.

-owncmap
       Try to use a PseudoColor visual and a private colormap. This allows the VNC server to control  the
       colormap.

-truecolour, -truecolor
       Try to use a TrueColor visual.

-depth depth
       On  an  X server which supports multiple TrueColor visuals of different depths, attempt to use the
       specified one (in bits per pixel); if successful, this  depth  will  be  requested  from  the  VNC
       server.

-compresslevel level
       Use specified compression level (0..9) for "tight" and "zlib" encodings (TightVNC-specific). Level
       1 uses minimum of CPU time and achieves  weak  compression  ratios,  while  level  9  offers  best
       compression  but is slow in terms of CPU time consumption on the server side. Use high levels with
       very slow network connections, and  low  levels  when  working  over  high-speed  LANs.  It's  not
       recommended to use compression level 0, reasonable choices start from the level 1.

-quality level
       Use  the specified JPEG quality level (0..9) for the "tight" encoding (TightVNC-specific). Quality
       level 0 denotes bad image quality but very impressive compression ratios,  while  level  9  offers
       very  good  image  quality at lower compression ratios. Note that the "tight" encoder uses JPEG to
       encode only those screen areas that look suitable for lossy compression, so quality level  0  does
       not always mean unacceptable image quality.

-nojpeg
       Disable  lossy JPEG compression in Tight encoding (TightVNC-specific).  Disabling JPEG compression
       is not a good idea in typical cases, as that makes the Tight encoder  less  efficient.  You  might
       want  to  use  this option if it's absolutely necessary to achieve perfect image quality (see also
       the -quality option).

-nocursorshape
       Disable cursor shape updates, protocol extensions used to handle remote cursor  movements  locally
       on  the  client  side (TightVNC-specific). Using cursor shape updates decreases delays with remote
       cursor movements, and can improve bandwidth usage dramatically.

-x11cursor
       Use a real X11 cursor with X-style cursor shape updates, instead of drawing the remote  cursor  on
       the framebuffer. This option also disables the dot cursor, and disables cursor position updates in
       non-fullscreen mode.

-autopass
       Read a plain-text password from stdin. This option affects only the standard VNC authentication.