opera

View documentation for the original command

$ tldr chromium

opera [OPTIONS...] [URL]

URL
    Specifies a URL to open upon launch. If omitted, Opera starts with its default homepage or last session.

--new-window
    Opens the specified URL or the default page in a new browser window.

--new-tab
    Opens the specified URL in a new tab within an existing Opera window, or in a new window if none are open.

--incognito
--private
    Launches Opera in a private browsing window (similar to Incognito mode in Chrome). All browsing data for that session will be cleared upon closing.

--profile-directory=name
    Specifies the profile directory to use. For example, 'Default' or 'Profile 1'. This is useful for managing multiple user profiles.

--user-data-dir=path
    Sets the base directory for user data, which includes profiles, cache, and other browser data. Useful for portable installations or specific testing environments.

--version
    Prints the current version of the Opera browser to the console.

--help
    Displays a list of available command-line options and their descriptions.

--remote-debugging-port=port
    Enables remote debugging via the specified port. This is primarily used by web developers for inspecting web content or browser internals.

--disable-gpu
    Disables GPU hardware acceleration. Useful for troubleshooting rendering issues or on systems with problematic graphics drivers.

The opera command provides a command-line interface for launching and interacting with the Opera web browser. While most users typically launch Opera via its graphical icon, the command line offers advanced control for specific use cases, such as opening particular URLs, managing browser profiles, or enabling debugging features. It is especially useful for scripting, automation, or troubleshooting browser behavior.

The command allows users to specify an initial URL to open, choose whether to open it in a new window or tab, or even in a private browsing session. Given that Opera is built on the Chromium engine, many of its command-line arguments are inherited from Chromium, providing a rich set of options for fine-tuning browser behavior, although not all Chromium options are directly applicable or documented for Opera.

Many of Opera's command-line options are inherited from its underlying Chromium engine. Consequently, the specific options available and their behavior can vary slightly between Opera versions, as well as between different Chromium releases. Some advanced Chromium flags might not be officially supported or may have unexpected effects in Opera. It's always advisable to consult the specific Opera documentation or use --help for the installed version.

Due to Opera's reliance on the Chromium engine, a vast number of command-line flags available for Chromium and Google Chrome can also be used with opera. These include options for proxy settings, security features, experimental flags, and more. Users interested in deeper control might explore Chromium documentation for additional potential flags, but should do so with caution.

The --profile-directory and --user-data-dir options are critical for advanced users and developers. They allow launching Opera with a specific user profile or storing all browser data in a custom location, which is invaluable for testing, maintaining separate environments (e.g., work vs. personal), or creating portable installations of the browser.

Opera has a long history, dating back to 1995. Originally developed by Opera Software ASA, it used its own proprietary rendering engine, Presto, until 2013. In 2013, Opera transitioned to the Chromium engine, which is maintained by Google. This shift significantly changed the browser's architecture, including its command-line interface. Consequently, many of the command-line options available for opera today are largely identical to those found in Chromium-based browsers like Google Chrome, reflecting the shared codebase and functionalities.

firefox(1), chromium(1), google-chrome(1), xdg-open(1)