Kameleo has a few technical terms used throughout the documentation and the website, so we'll document the meanings of some of these terms here.
Spoofing is the process of altering your device’s identifying information. In this case, Kameleo changes your browser fingerprint for every browser you launch.
Base profiles are real-world browser fingerprint configurations that are used for instantiating virtual browser profiles. This way the browser profile will have a consistent footprint after the spoofing mechanism is applied as most data are derived from a real browser. The rest of the data are generated automatically upon creation. You can filter in hundreds of thousands of base profiles to have profiles with the required language, operating system, and browser.
If you create multiple virtual browser profiles from the same base profile, they will have different browser fingerprints but both will remain natural.
Virtual Browser Profile
A Virtual Browser Profile contains all parts of the browser fingerprint with its settings and all the browsing data. This way, every profile will have a different configuration and websites will see it as another computer. Every time you reopen a profile you will be able to continue your work, as history, cookies, logins, passwords, bookmarks are all stored in them.
Profile's Lifetime States
Virtual Browser Profiles can have different states during their entire lifetime.
- Created: New profiles are in the Created state by default.
- Starting: When a profile is launching it is in the Starting state.
- Running: When the browser is launched and it is ready to operate, the profile will switch from Starting to Running state.
- Terminating: When the profile stopped it will change from Running to Terminated. While this happens and the browser quits, the profile is in the Terminating state.
- Terminated: Once the profile is stopped and all data is handled by Kameleo the profile goes into the Terminated state. It is ready to be saved or restarted.
Profile's Persistence States
Virtual Browser Profiles only have two different states for their persistence.
- Unsaved: When a profile is freshly created, edited, or the browser is started, the profile will have this state. If you would like to keep its state for future use after you remove the profile, you have to save it.
- Saved: After a successful save to a
.kameleofile, the profile will change to this state. In this state, you can safely remove the profile from Kameleo and reload it later at any time.
Kameleo is shipped with 4 fully functioning browsers:
- Custom-built Chromium
- Custom-built Firefox
- Unmodified Google Chrome
- Unmodified Microsoft Edge
Launcher is the browser environment you want to use to emulate a browser fingerprint configuration. Base Profiles and browser fingerprint settings will determine how websites will see your browser after the spoofing mechanism is applied. The launcher option sets which browser will open when you start a profile. If you set the Launcher option to Automatic, the browser will be selected by the table below.
|Device Type of the Base Profile||Browser Product of the Base Profile||Browser Engine started|
We recommend you use the automatic option because it will provide the best results. However, many Edge users prefer to use Chromium as their launcher.
Desktop profiles are Base Profiles that are visible as desktop browsers by websites and they are emulated in the built-in browsers by default.
Mobile profiles are Base Profiles that are visible as mobile browsers by websites and they are emulated by the Kameleo Mobile App by default.
No browser automation is available for mobile profiles at this time.
External Spoofing Engine
When a profile's Launcher option is set to External, or when you are running Mobile Profiles, the External Spoofing Engine will start. The External Spoofing Engine is a separate process that is managed by the CLI component. External browsers (such as the Kameleo Mobile App running on your device) can connect to it as an HTTP proxy and the Spoofing mechanism will be applied to the browser this way.
CLI Component / Headless Mode
Kameleo's core logic is implemented in the CLI component. The GUI component is using the API that is provided by the CLI. It makes the interaction easy with Kameleo. If you want to automate Kameleo you only need to run the CLI component (Kameleo.CLI.exe). You will be able to do everything from your script that you can do on the GUI.
By default, Kameleo is installed at the following location:
Checking the log files when you encounter problems is helpful to get a better understanding of how Kameleo works. The log files are generated in the Logs folder on a daily basis. As Kameleo has multiple components, each one creates its own file named after the following pattern:
By default, the Logs folder is available at the following location: