Frequently Asked Questions

Toggle visual edit mode via the button in the top bar, or use Option+E on Mac.

Currently, Flint agent controls typography, font size, etc., so you can change any styling via chat. Only changing copy on simple elements is supported at this time. More direct style editing is on our future roadmap.

Flint does not currently support dynamic drag-and-drop editing. To reorder sections and elements, use Flint chat editing.

On self-serve plans, Flint uses the design system imported from your website. For enterprise and custom plans, we offer integration with Figma and live codebases.

Flint agent keeps changes within the existing design system and will not expand on styling unless explicitly directed to do so. On custom plans, admin users can sync Flint sites with their design system automatically or work with the Flint team directly.

Not currently on self-serve plans. The workaround is to take screenshots of the Figma file you're referencing. On the custom plan, we support design system import from Figma.

Flint can help implement your rebrand. Provide a homepage built out in the new components, and Flint can scrape that design system into Flint. From there, Flint can migrate all old pages to use the new brand using AI.

Vite. There's no server-side logic at this time.

Yes! Flint agent creates mobile responsive components naturally. You can check the mobile view by clicking the device button at the top of the screen in edit view. If elements are not behaving as desired, Flint agent can make requested changes via chat.

Performance & Hosting: We use Vercel to host and deploy sites. Vercel is a trusted partner that supports the Fortune 500. Security: We encrypt all data at rest and in transit, use strong access controls, and never train on customer data by default. Flint undergoes annual SOC 2 Type II audits. See tryflint.com/security for more information. Support: We have SLAs and uptime guarantees on the custom plan. Support team is available 9am-5pm PT and responds during SEV1 and SEV2 events. Monitoring: Customers typically integrate Flint with their monitoring service (e.g., Datadog) by adding their script to the custom code section.

Flint agent auto-optimizes for fast page speed as it's critical for conversion, ranking, and user experience. You can test page speed on example Flint pages yourself. Note that page speed may decrease if you add resource-intensive features like complex animations, large unoptimized images, or blocking client-side JavaScript. To mitigate performance issues, you can instruct Flint agent to optimize your site: it will lazy-load images, defer non-critical scripts, and minimize render-blocking resources where possible.

Flint does not currently support self-hosting. We use industry-standard practices and work with trusted infrastructure providers to ensure your site remains secure and performant. For enterprise customers, we offer custom support and can discuss additional requirements.

We do not support code access on self-serve plans. On custom plans, we can support read-only access to code.

No. That said, there might be migration tools online for importing your Flint pages into other tools.

We don't currently support multiplayer editing. For now, only one person can edit at a time. When someone else on your team is editing, you can observe their progress or take over using the top bar when needed.

Yes. We may decline signup or import requests in some cases, including when: • Your site features complex layouts, custom code, advanced animations, or certain libraries that we do not currently support. • We can't access your site. This can happen if the site is blocked, restricted, requires login, has security protections, or has other technical limitations that prevent us from retrieving the content we need. • The use case isn't a fit for our platform. We currently do not support personal use, investor/VC diligence use, or business/competitive intelligence use cases. If you believe your signup or import was declined in error, or you need support to get your site imported, please contact us at support@tryflint.com.

Yes! We serve many D2C companies like Pliability, Minoan, and Seoul Beauty Club. We support Shopify stores, but they'll need to integrate via the GraphQL APIs. See Vercel's guide on building e-commerce sites with Next.js and Shopify for integration details.

Yes: you get a set amount of credits or 7 days, whichever comes first.

Two main ways: 1) more design variations and 2) targeted pages per keyword. See an example at tryflint.com/customers/graphite.

Use the Share button to generate a preview link of your current changes. Share it with your team for review. When you're ready to publish, Flint's AI generates a summary of all changes since your last publish, making it easy to confirm what's going live.

Ask the Flint agent to translate the page and it can either create a page for each language or create a toggle for the user to pick between languages. Flint only suggests translations and we advise you to manually review its output. If you want to use your translation agency, you can load in their translated outputs into Flint agent or give the agency direct access to Flint.

Yes! Flint only requires that the spreadsheet is copied into the chat or screenshots of it are added, with a concise description of what the spreadsheet represents and how its formulas work.

Flint supports dynamic landing pages that change based on which ad a user clicked. You can pass the campaign or ad name via URL parameters and the page updates accordingly. The caveat is that the content itself needs to be pre-generated: you'll build the variants in Flint in advance rather than generating them on the fly at click time. If you need true real-time AI generation at the moment of click, Flint is not the best fit. See Query Parameters for setup details.

24-72 hours.

Most customers are live within 1-5 days of onboarding. This time consists of: 1) Site import: 24-72 hours after signup. Your brand and analytics scripts are imported automatically. 2) One-time engineering setup: Custom analytics code and domain configuration take 15 minutes to 1 hour. 3) (Only for SEO) Google Search Console: Setting up the Flint sitemap in GSC so Google can find and index Flint pages. You may also link the Flint landing pages from your main homepage.

Export your Notion page or Google Doc as a PDF and upload it to Flint agent by clicking "Upload files" in the chat.

Not yet. For now, export your data into files and upload them into Flint chat.

Not directly, but you can convert it to CSV and copy/paste the contents into Flint chat. Flint can then use that data to create your page.

Customers have successfully performed full migrations by themselves. See our Migration Guide for step-by-step instructions. Enterprise customers can also get managed migration services—contact sales@tryflint.com for details.