Advertising
At most one ad on a page, and never near your files.
The publisher account is connected for review. No advertising unit is active yet. Advertising pays for the free tools, but it never sits inside the file picker, processing controls, results or download actions.
- One unit per page
- No stack of banners, refresh loop, sticky rail or full-screen interruption.
- Outside the task
- A reserved horizontal space keeps the ad away from the download buttons and stops the page jumping when it loads.
- Your file is never ad input
- The ad does not receive the selected file, its name, its pixels, the PDF contents or the result.
What the ad provider can receive
When advertising is active, Google AdSense receives an ordinary ad request. That can include an IP address, browser and device information, the page being viewed and consent signals. Depending on your region and choices, Google may use cookies or local storage. The integrated Google consent message supplies the available choices where required.
What stays separate
File processing remains entirely inside this browser. The image and PDF engines do not
pass a File, filename, output blob or processing setting to the advertising
code. The ad is a separate page element and is never styled as a tool action.
Format policy
Only one manually placed, responsive display unit is allowed. Auto Ads, anchor ads, vignettes, pop-ups, autoplay, forced waits and automatic refreshes are deliberately absent.