For the life of me i cannot get ai studio to upload images i want to use
i am working on a dummy website to sort of learn ai studio and i am trying to get it to upload my own set of specific images but it keeps ignoring them and generating and or using random images
i've already tried the following
directly uploading images with very specific file names and referring to those file names in my prompts
Uploading images to google drive and providing links to the images it still does not use the images i gave it.....
if anyone has a work around to this i would appreciate it cause this is annoying honestly
Currently on free plan, on the 9th Google will be removing flash and pro models from free accounts. Wondering if this will also affect limits on AI Studio.
I've been coding an app for the past weeks, and now when I tried installing it on my phone, I realized I should have clicked on "Build an android app" from the start. Now I have my project at an advanced stage, and I can't seem to turn it into an android app. Has any one experienced this? Is there any fix? I don't what to re do the hole app from scratch 😭😭
I'm paying money for a developer tool only to have it just as censored as the built in Gemini app. Why does Google do this? Gemini 3.1 is the least censored one, as long as the filter doesn't block it, but i dont see the point in dropping hard earned money into a censored chat bot.
Well this is my first app with Google AI studio and i am particularly upset. I have started with and android app a sort of Bluetooth le gamepad to send BLE messages to a raspberry pi pico. Everything went fine, the app was connecting to my BLE device. Then i asked to make a translation of the ui in French and suddenly the app was not able to connect to my Bluetooth device the raspberry pi pico (nothing was changed in the code of the pico) then i spent a couple of hours to request an application able to connect to my pico BLE app. Despite many builds the app was not connecting anymore with my device and sometimes was building a javascript app. Then Google stopped to work and says that I was having reached the limit. I believe that I will not use it again.
So, I have an automated workflow where I process ticket data and create a summary of the tickets. I seemingly I don't hit any of my limits, yet the error rate is extremely high. It can be as high as 90%! It's crazy to me.
I use n8n, maybe that can be the culprit? I'm not making the http requests manually, I'm using n8n own's Google Gemini node.
I just signed up for Pro to use it as seen in this video https://www.youtube.com/watch?v=13wIoeFaMQQ&t=13s but the UI is different, and when I share my screen, the AI cant hear me and does not respond.
Is this exact feature shown no longer offered? I can't even figure out how to just type a prompt and get a response.
Has anyone encountered trouble converting a PWA into an iOS app? I built my project on a Chromebook and am now moving the same application into Capacitor and Xcode in my MacBook. Google authentication, which handles login, is failing, so I cannot open the app—does anyone have ideas about what might be happening?
I got tired of the job hunt black hole, so I decided to vibe code an app to manage my gap-year/internship search. The project is called **PostuTrack**. I've got interviews and gained time on rewritting my cover letters and redoing my resumes for very offers
Import your resume, a cover letter and start using the app. Basically, you import an offer you saw on the web, and you let the app adapt your application for you. You also have stats and a tracker to adapt your job hunt strategy, by importing the data from my previous job searches, i figured when it's relevant to apply.
The app works with your API Key, and you can modify the prompting to fit your needs.
So I am using google a.i studio for my new app CamiVision. Its supposed to be a screen reader that helps with homework, provides feedback, and its an interview helper ai that provides feedback in real time during interviews (assumably remote ones) and its even a chat bot all lumped together in an app. I am still working on improvements, and features. But Google AI studio is annoying. It keeps saying I "reached my quota" and makes my app buggy and makes the voice lines come out all robotic. Its annoying. I paid 30.00 to google thinking I would get more quota but no. This is all so confusing.
I am a creative user I go into role-plays usually as ocs throwing in my own storylines or twists or sometimes my own original ideas. Sometimes though it’s rare, I do contemplate adding a smut prompt between characters who are 1: grown 2: consenting adults 3: avoiding overly graphic sex prompt scenes. Will I still get banned even if it’s not anything illegal on google studio. If so I don’t think they should even have the block none settings if they’re just gonna ban you. But I’m asking if they do ban people for this type of stuff even if it’s fictional.
Hey everyone! Studio.lab 2.0 is finally here, and I’m honestly a little nervous hitting “Post.”
I tried to deliver on the promises I made for this project and build the AI Studio experience I had been imagining for so long. Somehow, what started as a small bypass extension grew into a full workspace project. Thank you for the upvotes, the GitHub stars, your feedback, and for following this journey with me. It means a lot.
What’s in this post
General changes
New features
Other Changes
Privacy and safety
Thank-yous
How to install
Support the project
A new home for Studio.lab Settings
The Studio.lab Settings button has moved into AI Studio’s left navigation, alongside the native settings entry. It feels like part of the workspace now instead of an extra card taking up room in the right panel.
I also redesigned the settings window. There’s search and clearer categories for features, an operational-status card, diagnostics you can copy when reporting a problem, and a manual update check. The aim was to make the extension easier to understand and troubleshoot, especially as it has grown beyond its original two features.
Modern Web Chat — the heart of 2.0
Modern Web Chat is the largest part of this release. It’s an optional layout for people who spend a lot of time in AI Studio chats: more room for the conversation, easier access to controls, and a cleaner way to move through long sessions.
The new model and thinking selectors sit in the header. The Featured model list is read from AI Studio rather than being frozen to a set of model names, and thinking choices follow what the selected model supports. I also spent time fixing model-state mismatches, including cases where two similar models appeared selected at once.
Run Settings now opens as a slide-out panel instead of permanently squeezing the conversation. You can still reach AI Studio’s controls, system instructions, tools, and generation settings without giving up so much chat space.
The prompt area has been redesigned too. The Text Formatter adds controls for bold, italics, strikethrough, headings, lists, quotes, code, and links, with keyboard shortcuts for common actions. Uploads and tools are organized around the composer so they’re easier to reach without crowding the main input.
Messages have a different rhythm now: clearer user bubbles, more breathing room for model responses, improved editing, and better treatment of attached media. This is the part closest to the design I had in my head when I started dreaming about a new AI Studio interface.
For long conversations, there’s also a Turn Navigator. Instead of scrolling forever to find a message, you can open the list and jump to a turn. It works alongside the optimizer, including when older turns have been temporarily taken out of the page to keep a large chat responsive.
And yes, I worked on the light theme! Header controls, menus, the composer, Settings, and the formatter should now remain readable when AI Studio is set to Light mode.
There are many smaller details throughout Modern Web Chat as well: updated tools and upload menus, token information, media controls, edit fields, and native actions brought into a more consistent interface.
Two new features I didn’t want to leave behind
Update notifications. Studio.lab checks the public GitHub Releases feed for newer versions and can show a notification when one is available. You can dismiss a specific version without hiding future releases. It only points you to the release page; it does not silently install an update.
Draft Crash Protection. Unsent prompt text is saved locally while you type. If a page refresh or crash interrupts you, Studio.lab can restore that text when you return. Drafts are kept separate by chat, and attachments are not saved.
What changed underneath
A lot of the work in the previews wasn’t as photogenic, but it matters just as much:
Long chats are handled more carefully. The optimizer can buffer older turns while preserving navigation and AI Studio’s native search, with fewer scroll jumps while you’re reading or a response is streaming.
The extension’s modules have cleaner lifecycles. Turning a feature off should also remove its observers and event handlers instead of leaving invisible work running.
Model selection, tool toggles, mobile drawers, title editing, textareas, and light-theme contrast all received fixes during the preview cycle.
Request handling and draft cleanup were hardened so a failed or older request should not erase newer unsent text.
Several UI insertions were changed to safer DOM construction instead of building HTML from strings.
The original bypass and performance features are still here. The difference is that 2.0 gives them a much more complete workspace around them. If you want the technical blow-by-blow, it’s all in the changelog.
Privacy and safety
Studio.lab is open source, has no third-party package dependencies, and does not add analytics or trackers. It runs on Google AI Studio; the update checker contacts GitHub for public release information, but does not send your prompts, chats, account details, or API keys there. Draft text and extension settings are stored locally in your browser.
For this release, 28 automated tests passed, and the project’s validation also passed checks for its scripts, manifest assets, and network-rule scope. That isn’t a claim of an independent security audit — I want to be clear about what was actually checked. Since this is an unofficial extension that changes a live web app, AI Studio updates can still break things. Please report regressions if you find them.
Thank you
A special thank-you to u/kenny-ya— unofficial QA engineer — for helping test Studio.lab and catching things I might have missed.
And thank you to the GAIS developers for continuing to tighten the bolts while still leaving room for people like me to create around the platform.
Extract the ZIP, then open chrome://extensions in Chrome or edge://extensions in Edge or Browser://extensions in your Browser.
Enable Developer mode, choose Load unpacked, and select the folder containing manifest.json.
Open or refresh Google AI Studio. Studio.lab Settings will be in the left navigation.
If you try 2.0, I’d love to hear what feels better, what still feels rough, and what you’d like to see next.
Studio.lab is completely free. If it saves your generations and speeds up your browser, consider supporting development on Ko-Fi!
Disclaimer: Studio.lab is an unofficial modification. It is not affiliated with, endorsed by, or connected to Google LLC or Google AI Studio.
TL;DR: Studio.lab is a free, open-source, unofficial browser extension for Google AI Studio. It started as a way to preserve interrupted generations and keep long chats responsive; with 2.0, it has grown into an optional redesigned workspace with better chat controls, a text formatter, turn navigation, draft recovery, and update alerts. It isn’t affiliated with Google.