Project Settings
🔗 Original Page — Source of this material
Description
These settings allow you to fine-tune your project’s operation. They determine which parameters will be automatically applied when the template is launched.
How to open the settings?
To open the project settings, you need to click the corresponding button in the static blocks panel. If you don’t see the static blocks, right-click on an empty area of the workspace and check the “Show static blocks” option in the context menu.
The project settings contain 3 sections: browser settings, proxy checker settings, and HTTP settings.
Browser Settings
Quick Setup
You can choose between 2 quick setup options from templates — Quality or Speed. Depending on your choice, the general browser settings will be auto-configured, but you can adjust each option individually if you wish.
Saving Settings
If you often use the same combination of settings in your projects, you can save it using the corresponding button (1). After clicking it, you’ll be prompted to enter a name for the new configuration.
Only the settings from the “Browser” and “Proxy Checker” tabs will be saved. Settings from the “HTTP” tab are not saved.
To delete a configuration, use the corresponding button (2).
Browser Type
In version 7.5.0.0, the Chromium engine was added. The Chrome engine was renamed to CEF (Chrome).
Choose which browser to use in your project. Several options are available. You can also switch browsers during project execution using the ❗→ Browser Settings action. In the ❗→ program settings, you can set the default browser for all new projects.
Arguments
For the Chrome browser, you can add custom startup arguments separated by spaces. You can find the full list of arguments at the following links: https://www.chromium.org/developers/how-tos/run-chromium-with-flags https://peter.sh/experiments/chromium-command-line-switches/
After changing the arguments, you need to restart the browser. You can do this by clicking the “Restart” button or by executing the “❗→ Launch Instance” action.
Input Emulation
Allows you to emulate real user actions when filling out fields on web pages, clicking buttons and links, which helps to bypass website protections. You can select from 4 preset options using the slider, choosing between project speed and quality. With maximum speed, all emulation and protection bypass options are disabled. With maximum quality, all emulation and protection bypass options are enabled, but execution speed will be lower.
- DOM events emulation — Emulates common DOM events via JS (such as onfocus, etc.). These events are tracked by scripts that add new fields to the web page, check field filling, or implement basic anti-bot checks.
- Text input emulation — Emulates data entry and page interaction through keyboard and mouse events, as if a real person is typing and clicking. Bypasses advanced protections that monitor input not using peripheral devices.
- Neural protection bypass — Advanced emulation that takes human behavior into account. Allows you to bypass most bot protection algorithms, including neural network-based ones.
Full Mouse Emulation
This option enables mouse emulation at the project level. This means that when executing “❗→ Set Value” (Set) and “❗→ Perform Action” (Rise) actions, mouse emulation from the current cursor to the specified HTML element will be automatically added.
So, to enable mouse emulation in your template, just one click is enough! Nothing else is required.
Works only with maximum input emulation quality.
Demonstration
Do Not Use Browser
Disables the browser component, so you can’t interact with the page and its elements. If you work via POST/GET requests, databases, or command files, you can disable the browser to improve performance.
For more information on working with requests, see the articles ❗→ GET Request, ❗→ POST Request and ❗→ HTTP Requests.
Browser Without Rendering Content
Allows you to keep loading all elements on the page, but without displaying them. This helps to save computer resources.
Dedicated Process
If enabled, uses one instance per base.exe database — in this case, tasks inside the database will be executed faster, but resource consumption will increase.
This setting is available only for the Firefox engine.
Use Proxifier
Allows you to use a program for proxying network traffic in your template.
This setting is available only for the Firefox engine.
Load Images
For most websites, projects can work without images. Disabling them significantly saves traffic. You can also disable images via the ❗→ Browser Settings action.
Load Objects (Flash, Silverlight, Java)
If disabled, Flash, Silverlight, and Java objects will not load or run on the page. This helps boost performance and reduce traffic usage. You can also control this setting via the ❗→ Browser Settings action.
If Flash is enabled in these settings but doesn’t work for some reason in the Chrome browser, add the ❗→ launch arguments --enable-system-flash --disable-software-rasterizer --disable-smooth-scrolling to the launch parameters. More info: Flash not working in browser
Run JavaScript
If disabled, scripts on the page will not execute. For most modern resources, this may affect website functionality. You can also control this setting via the ❗→ Browser Settings action.
Clear Cache
Automically clear the contents of the cache (temporary storage) at the start of the project. Using the cache helps save traffic. You can also control this setting via the ❗→ Browser Settings action.
Some of these settings relate to content loading rules and can be changed during operation in the ❗→ browser window.
Proxy Checker Settings
Allows you to set the rule by which proxies will be used from the proxy checker when the project starts.
You can also change the rule for the proxy checker within the project using the “Get proxy” action. For more details, see the article ❗→ Using Proxies.
HTTP Settings
Sets the method for sending HTTP requests — Standard or Alternative. The “Default” option is configured in the ❗→ program settings under the "Execution" tab.
By default, ZennoPoster uses the Chillkat library to send HTTP requests. We have added an alternative option — ZennoHttpClient, which can resolve issues with some websites (for example, Yandex).
- Default — the method selected in the ❗→ program settings.
- Standard — Chillkat.
- Alternative — ZennoHttpClient.
These settings are used for working with request actions. For more information about working with requests, see the articles ❗→ GET Request, ❗→ POST Request and ❗→ HTTP Requests.