Getting Started with Cutiepage: The Complete Guide to Building a Personalised Website Gift in Minutes

Why a website can be the most thoughtful gift you've ever sent

We're used to the idea that a gift is an object. A box. Something wrapped in paper. Something that ships. But the truth is that most of the gifts we remember forever aren't objects at all — they're moments.

A mixtape someone burned in 2008. A handwritten note slid under a door. A playlist sent on a difficult Tuesday. The physical medium wasn't the point; the thought was.

Cutiepage is built around that realisation. Instead of another mug or another keychain, we let you send a tiny website — a personal microsite, really — that lives on the internet at a link you control.

It's quick to set up, easy to customise, and the person receiving it can open it on their phone the moment they get the message. No delivery delays. No shipping address. No 'the package got stuck at customs'.

Just a link, and on the other side of that link, something that was very clearly made for them.

That's what this guide is about. If you've landed on Cutiepage and you're wondering what to actually do next, this post walks you through the whole thing, from the first time you open the templates page to the moment you hit send.

We've also written it so that if you're thinking about signing up but haven't yet, you'll know exactly what you're committing to before you put in any time.

This is the post we wish had existed when we first started showing Cutiepage to friends. They kept asking the same practical questions — 'how long does it stay up', 'what happens if I make a mistake', 'can my mum use this' — and it became obvious that a long, honest answer to all of those in one place would be more useful than any marketing page.

So consider this the long, honest answer.

What Cutiepage actually is (and what it isn't)

Cutiepage is a platform for creating beautiful, customisable microsites — usually for personal occasions like birthdays, anniversaries, proposals, and the kind of little everyday surprises that deserve more than a text.

You pick a template, fill in details that make it yours (names, photos, inside jokes, playlist links, memories, whatever fits), and publish it to a private-feeling public URL that you can share with one person or a hundred.

It is not a website builder in the traditional sense. You're not designing a landing page for your new SaaS. You're not negotiating with a grid system. You're not expected to know anything about code, hosting, or design.

Every template is a self-contained experience where all the decisions that are hard to make — typography pairing, spacing, colour palette, responsive breakpoints, how animations ease in and out — are already made for you.

Your job is the fun part: the words, the pictures, the memories.

The difference matters. A traditional website builder gives you a blank page and calls that freedom. Cutiepage gives you a finished page that's already lovely, and asks you to make it specifically for one person.

The first approach is empowering if you're a designer. The second is empowering if you're a human being trying to do something nice for another human being on a specific Sunday.

We've deliberately chosen the second approach. We think there are already enough blank-canvas website builders in the world, and not enough tools that say 'you don't need to be a designer — you just need to care about someone'.

The occasions Cutiepage works beautifully for

Birthdays are the most common use case, and for good reason. A birthday is annual, it's personal, and it's an occasion where everyone already expects some kind of gesture — but where most gestures feel indistinguishable from every other year's.

A microsite is different. It's specific to the person and specific to the year. It sits in the chat thread long after the cake is gone, and it's the thing they scroll back to weeks later when they want to feel remembered.

Anniversaries are the second most common. Couples use them for month-aversaries when they're new, year-aversaries when they're established, and occasionally for very particular anniversaries — the anniversary of the first date, the anniversary of moving in together, the anniversary of a specific vacation.

The platform is flexible enough to handle all of these without feeling generic, because every template was designed to be filled in with specific details rather than generic well-wishes.

Proposals are a smaller use case but a meaningful one. A few people have used Cutiepage to build microsites that walk a partner through the story of the relationship before asking the big question. We're careful here — we'd never suggest that a website replaces an in-person moment — but as an accompaniment, it can be extraordinary.

Graduations, new jobs, exam results, recovered-from-a-hard-year markers — these are the occasions people don't always celebrate formally, but that often deserve it more than the big ones. A microsite for a friend who just got through a hard chapter can be one of the most meaningful things you ever send them.

And then there are the no-occasion occasions. The 'I was thinking about you' microsite. The 'we've been friends for a decade and I never said this properly' microsite. The 'here is why you matter' microsite on a day that wasn't special until it was.

Step one: browse the templates and trust your gut

When you open the templates page, you'll see a grid of microsite designs, each with a preview image and a short description.

Resist the urge to open all of them at once. The templates are meant to feel different from each other — some are playful, some are elegant, some are structured like a long scroll of memories, some are single-screen love letters — and the one that's right for you will usually announce itself in the first few seconds.

A few practical notes.

Every template is fully responsive, which means it will look good on a phone, a tablet, and a laptop with equal care. You don't have to worry about choosing a 'mobile version'.

Every template also supports the same core content types — text, images, links — so the choice between templates is really about feel, not about features.

Pick the one that matches the vibe of the relationship and the occasion, not the one with the most boxes to fill.

If you're completely stuck, here's a small heuristic that works well: imagine the person receiving the site opening it on their phone during their morning coffee. Which of these templates, scrolled through in that specific moment, would make them smile?

That's the one.

A second heuristic that also works: pick the template that makes you feel something when you preview it with placeholder content. If the empty version already stirs an emotion, the filled-in version will stir it harder.

Don't pick the template that looks most 'professional'. This isn't a job application. This is a gift.

Free vs paid templates — how pricing works

Some of our templates are completely free.

You can customise them, publish them, and share them without paying anything, and they stay live at their URL for as long as Cutiepage exists.

They're a great way to try the product — you can make something real, share it with someone, and see how the whole experience feels before you decide whether a paid template is worth it.

Paid templates are one-time purchases. There are no subscriptions, no recurring charges, and no surprise renewals.

You pay once, you get the template, you publish as many times as you want with your own customisations, and that's the end of the transaction.

Prices are shown clearly on each template card and on the checkout page in Indian rupees, and payments run through Razorpay — which is the same checkout flow you've probably already used on dozens of Indian websites, with UPI, cards, netbanking, and wallets all supported.

A common question: why are some templates paid and others free?

The paid ones typically involve more elaborate layouts, custom illustrations, more interactive elements, or animations that took more time to design and ship.

The free ones are still beautiful — they're not a stripped-down version of anything — but they stay free because the cost to produce them was lower, and because we want everyone to be able to send something nice regardless of budget.

Another common question: do paid templates have extra features that free ones don't?

In a strict sense, no. The feature set is the same. What you're paying for is design depth — not more boxes to fill, but a richer final artefact.

Step two: customise without overthinking it

Once you've picked a template and started the customisation flow, you'll see a live editor on one side of the screen and a preview on the other.

As you type, the preview updates. This real-time feedback is, more than almost anything else we've built, the reason people don't abandon Cutiepage halfway through — you're never working in the dark, wondering what the final product will look like.

The fields you'll see depend on the template. A birthday template might ask for the recipient's name, a title message, a list of memories, and a photo. An anniversary template might ask for 'years together', a longer letter, and a gallery.

A proposal template might ask for very little text but a lot of visual breathing room.

There's no wrong number of fields to fill — if something feels optional to you, it probably is. Leaving a section blank usually just means that section gracefully disappears from the final site.

The one piece of advice we give everyone: don't try to write your message in the editor for the first time.

Write it somewhere else first — a notes app, a piece of paper, the back of a receipt. Get the words right, then paste them in.

The editor is for assembling, not drafting. You'll end up with something warmer and more specific if you treat the two stages separately.

The second piece of advice: don't try to be funny in places where sincere would work better. Humour is easy to over-apply when you're writing under mild pressure, and the resulting microsite can feel like it's hedging against its own emotional weight.

If you mean it, say it plainly. The template's visual design will handle the elegance. Your words just have to be true.

Writing the message: a small field guide

The hardest part of any Cutiepage is almost never the design. It's the writing.

People freeze. They stare at a blank text field labelled 'message' and either write nothing or write too much. Here's how we'd think about it.

Start with one specific memory. Not a summary of the relationship, not a list of qualities, not a timeline. One specific thing that happened — a Tuesday, a road trip, a moment in a kitchen.

Describe it in a few sentences. Don't editorialise. Just let the detail do the work.

Then, after the specific memory, say one honest thing about how the person makes you feel. One line. Not a paragraph.

Then stop. Resist the urge to pad it out with generic well-wishes. 'Happy birthday, I hope this year is amazing' is almost always worse than the specific thing you already wrote.

If you're writing for a friend, the rules are the same but the register is slightly different — more humour is allowed, and more reference to shared in-jokes.

If you're writing for a parent, the temptation to be generic is enormous, because you've never said the sincere thing out loud and writing it feels strange. Write it anyway. That's the whole point.

If you're writing for a partner, keep it concrete. Every relationship has private language, private references, small moments that nobody else would understand. Those are the parts that land hardest in a microsite, because they're the parts that nobody else could have written.

Uploading photos and getting them to look good

Most templates let you upload photos directly.

We run these through Cloudinary behind the scenes, which handles resizing, format conversion, and delivery optimisation — so you can upload a 12 MB photo straight from your phone's camera roll and it'll still load quickly on a 3G connection in someone else's city.

You don't have to compress anything, crop anything, or worry about file formats. Upload what you have.

Two small tips, though.

First, square or near-square photos generally look better in microsite layouts than ultra-wide or ultra-tall ones — the templates are designed to work across screen sizes, and extreme aspect ratios can crop awkwardly on mobile.

Second, if you're using screenshots or images with text on them, double-check on a phone preview that the text is still readable. What looks fine on a laptop sometimes disappears on a 5-inch screen.

Photos don't have to be perfect. In fact, slightly imperfect photos — the candid ones, the ones that aren't posed — almost always work better than professional-looking shots.

The whole point of a Cutiepage is that it feels personal. The slightly blurry one from the trip in 2022 will do more emotional work than a stock photo ever could.

If you're tempted to pull photos from Google Images or stock sites, please don't. We can always tell. And more importantly, the recipient can always tell — not consciously, but they can feel it.

A slightly grainy photo you took yourself beats a pristine stock image every single time.

Choosing the cover photo specifically

Most templates have a hero or cover photo — the big image at the top of the site that sets the tone before any text is read.

This is the single most important photo choice you'll make, and it's worth spending a disproportionate amount of time on.

The cover photo does two jobs. It tells the recipient that the site is about them before they've even started reading, and it sets the emotional register for everything that follows.

A cover photo of the two of you from years ago establishes history. A cover photo from last week establishes immediacy. A photo of something they love (their dog, their hometown, a favourite dish) establishes knowing-them.

All three approaches work. Pick the one that matches what you want the first three seconds to feel like.

Avoid cover photos that are too busy — they compete with the title text. Avoid cover photos that are too dark if the template's title text is also dark. These are small practical issues that you'll catch in preview if you look carefully.

If you can't decide between two cover photos, flip a coin. You'll notice immediately which one you were hoping it would land on, and that's your answer.

Step three: preview everything before you pay

Before you pay for a paid template, you'll be able to preview the entire site — not a sample, but your actual site with your actual content — in a preview mode.

This is an intentional design choice. We want you to know exactly what you're getting before any money changes hands.

The preview URL is not the final URL. It's a temporary view, not indexed, not shareable beyond you, and it goes away after a little while.

Its only job is to let you see what the recipient will see.

Use it. Walk through the whole site from top to bottom on your phone, not your laptop, because your recipient will almost certainly be on their phone when they open the link.

A checklist we recommend running through at this stage.

Are all the names spelled correctly?

Is the date right? (People miss this surprisingly often.)

Do the photos load at the right sizes?

Does the music or video link actually play?

Does the final call-to-action say what you want it to say?

And — most importantly — does the site make you feel the thing you wanted the recipient to feel?

If the answer to the last question is 'yes', you're ready.

If the answer is 'not quite', the problem is almost never the template. It's one line of text somewhere that's slightly off, and you'll find it in one more pass.

Step four: paying securely

For paid templates, checkout runs through Razorpay.

You'll see the Razorpay window open with your payment options: UPI, credit and debit cards, netbanking, and popular wallets.

There's no Cutiepage account required for the actual payment step — Razorpay handles all of that in their own secure environment. The card or UPI details you enter never touch our servers.

After payment, you're redirected back to Cutiepage, your template is unlocked for publishing, and you'll receive an email receipt from Razorpay for your records.

If anything goes wrong during payment — the network drops, you hit cancel by accident, the bank declines the transaction — nothing bad happens to your work.

Your customisations are still saved. You can retry the payment without starting over.

Refunds are handled through our refund policy page, which is linked from the footer. The short version: if something genuinely didn't work and we can't make it right, we'll refund you.

We've tried to make the product good enough that this almost never comes up, but the policy is there because you deserve to know what you're committing to.

A note on fraud: we don't see your card details. Razorpay is PCI-DSS compliant and handles the payment UI inside their own iframe. If you've paid for anything on an Indian e-commerce site in the last few years, you've probably already trusted Razorpay without knowing it.

Step five: publishing and getting your link

Publishing is the last step, and it's the one that takes the least time.

You click publish, we do a few things on the server (upload any remaining assets, generate the final static pages, register your slug), and a moment later you get a URL that looks like cutiepage.com/your-slug.

The slug is the last bit of the URL — the part after the final slash. By default we generate something readable from the title you gave your site, but you can change it.

A few rules: slugs are lowercase, they use dashes instead of spaces, and they have to be unique across the platform. If the one you want is taken, you'll be prompted to pick another one.

Don't overthink this part. The person you're sending the site to isn't going to read the URL closely — they're going to tap it and open the site.

Once published, your site is live at that URL immediately.

You can share the URL however you want: send it in a message, paste it into an email, put it in a birthday card with a QR code, send it to a WhatsApp group, or keep it private and show it to one person.

Cutiepage doesn't gatekeep the link and doesn't require the recipient to sign up for anything to view it. They just open it.

Some people like to pick a slug that's meaningful — the recipient's nickname, the date, a private reference. Others just let us auto-generate one. Either approach is fine. The slug doesn't change the gift; it's just a small extra moment of delight if the recipient happens to notice.

Can I edit the site after publishing?

Yes. This is one of the features we get asked about the most.

Once a site is published, you can go back into the editor, make changes, and republish.

The URL stays the same, so any link you've already shared continues to work.

We keep a version history for paid templates, which means if you make a change and regret it, you can usually roll back to an earlier version without losing anything.

A common use case: you publish the site, send it to your partner, they mention that one of the photos is their least favourite one from that trip, and you quietly go back in, swap it out, and republish.

They open the link again tomorrow and see the update. No awkwardness, no new URL, no 'wait let me send you a different link'.

There are a few fields that are immutable after publishing — the template itself, for example, and the slug. If you want a different template or a different URL, you'd effectively be publishing a new site.

But everything that's content — text, photos, dates, links — is editable as many times as you need.

We've had users who publish a birthday microsite and then keep editing it once a year on the same date, using it as a living journal of one relationship. That wasn't something we designed for explicitly. It's just a nice emergent use.

How long does the site stay up?

Paid templates stay published indefinitely.

As long as Cutiepage is operating, your site stays at its URL. We don't have a subscription model where the site goes down if you stop paying, because you're not paying us recurringly in the first place.

You paid once. The site is yours.

Free templates also stay published, though we reserve the right to clean up free sites that have been abandoned for a very long time — mostly for storage hygiene reasons.

In practice this hasn't actually happened to anyone yet, and if it ever did, we'd reach out first.

In either case, you have full control from your dashboard.

You can unpublish a site whenever you want, which takes it off the internet immediately.

You can republish it later with no penalty.

And you can delete it entirely if you're done with it.

The 'indefinitely' promise is obviously conditional on the platform existing. We intend for Cutiepage to exist for a very long time, but if we ever had to shut it down, we'd notify everyone well in advance and provide an export option so that the work isn't lost.

Common mistakes we see (and how to avoid them)

The first and most common mistake is overwriting.

People often feel like if a microsite has three sections, they need to fill all three with a lot of text.

In practice, shorter is almost always better. A single perfectly chosen sentence does more than three paragraphs of preamble.

Trust the design to do the heavy lifting and let your words be specific instead of thorough.

The second is using generic photos.

A reverse image search of any stock wedding photo returns the same image on twenty other websites. Your recipient won't know why the site feels slightly hollow, but they'll feel it.

If you're choosing between a polished stock image and a slightly-less-polished real photo of you and them, pick the real photo every time.

The third is forgetting to preview on mobile.

We can tell you a hundred times that most recipients will open the site on a phone, and people will still design on a laptop and never check the phone preview.

Open the preview on your own phone before you send the link. It takes thirty seconds and it catches 90% of the small layout issues.

The fourth — and this is a small one, but it matters — is sending the link at the wrong time.

A birthday microsite sent at 11:47 pm on the day of the birthday feels completely different from one sent at 7:00 am when the person wakes up.

The content is identical. The gift, emotionally, is not.

Think about when you're hitting send, not just what you're sending.

The fifth is trying to include too much. A microsite isn't a scrapbook. You don't have to squeeze in every photo, every memory, every inside joke. Pick the five best things. The rest can live in your own memory.

The sixth is proofreading too quickly. Read every line out loud. Typos survive silent reading in a way they don't survive being spoken. It sounds silly. Do it anyway.

Sharing the link the right way

When you paste a Cutiepage URL into WhatsApp, iMessage, Instagram DMs, or most modern messaging apps, the app generates a link preview — a card with a title, a description, and a thumbnail image.

We've taken care to make sure these previews look good out of the box, but you can also customise the preview image for paid templates if you want a specific photo to be the 'first thing' your recipient sees before they even tap.

A tip that works well: send the link with no context.

No 'look what I made', no 'click this', no explanation. Just the link, naked, in a chat window.

The surprise of not knowing what the URL is landing you in is part of the gift. The page does its own introducing.

If you're sharing with a group — say, a microsite for a parent's birthday that siblings want to send together — we recommend one person being the designated sender.

Multiple people forwarding the same link to the same recipient can muddle the moment. Pick one person, send it once, let it land.

Another approach that works beautifully: put the link in a physical birthday card. A QR code printed in the corner, or just the URL written out by hand. The dual-medium gesture — the paper card and the digital site — feels much bigger than either would alone.

If you're giving the microsite in person, don't watch over the recipient's shoulder while they scroll. Give them the link and then walk away for a minute. They deserve to read it in private.

What happens on the recipient's end

From the recipient's side, the experience is intentionally simple.

They tap a link, a page loads, they scroll.

There's no login, no sign-up, no app to download, no cookie banner beyond the usual, no ads (on the microsites themselves — we'll come to that).

They just see the site you made for them.

The sites are fast. We render them as static pages wherever possible, which means the first load is usually under a second even on slow connections.

Images lazy-load as the recipient scrolls. Animations are tuned to not overwhelm — we've deliberately avoided the auto-playing music, the cursor sparkles, the kinds of touches that were charming in 2008 and exhausting now.

If your template includes interactive elements — a letter that unseals when tapped, a gallery that fades between photos, a countdown to a date — those all work without the recipient doing anything special.

No buttons to enable, no 'tap here to start'. The site behaves the way a thoughtful designer would want it to behave on the first visit.

Accessibility is something we care about and work on continuously. All of our templates ship with readable type sizes, sufficient colour contrast, and keyboard navigation support. If someone's using a screen reader or relying on larger system text, the site still works.

If a recipient opens the site on a slow connection — say, on the train, on data — we've tuned image loading so that the critical content renders first and the decorative touches fill in as bandwidth allows. Nobody's staring at a loading spinner for their birthday.

A note on our blog and ads

You might notice that this blog page — the one you're reading right now — has ads on it, and you might also have noticed that the microsites themselves do not.

That's intentional.

We think ads have no business being inside someone's gift. The site you make for your partner's birthday is not a page we're going to monetise with display advertising; that would be weird, and it would degrade the whole reason people come to Cutiepage.

The blog is a different thing. It's where we write tutorials, share design ideas, and occasionally talk about how to think about personal gifting in a world that mostly wants to sell you a mug.

The ads here help us keep the rest of the platform — including all the free templates — genuinely free. You're doing us a small favour just by reading. Thank you.

If you ever see an ad anywhere else on Cutiepage — on the homepage, on a template page, on a published microsite, on the checkout flow — that's a bug, and we'd appreciate you reporting it.

Ads are scoped to this blog and nowhere else.

We also want to be clear that the ads you see are served by Google AdSense. We don't control which specific ads appear — Google does that dynamically based on the page content and the viewer's context. If you ever see an ad that seems inappropriate, you can report it via the 'i' icon on the ad itself, and Google will take it into account for future impressions.

Dashboard and managing multiple sites

Once you've made one microsite, making the next one is much easier.

The dashboard shows all of your sites — published and unpublished — in a list, with quick actions to edit, preview, unpublish, duplicate, or delete each one.

Duplicating is a feature we added after watching people rebuild similar sites from scratch. If you make an anniversary site this year and want to make one next year with the same structure but different content, you can duplicate the old one, update the details, and publish under a new slug in a few minutes.

The dashboard also shows basic analytics for each site — how many times it's been opened, when it was last viewed — if you've opted in to that feature. Many people turn it off because they don't want to know. That's a valid choice, and it's the default.

Managing multiple sites is particularly useful for people who end up making Cutiepages for a lot of different occasions. A few users have essentially turned it into their default gifting tool, which was not something we predicted when we started, but which we're happy about.

What to make first if you're new

If you're reading this and you've never used Cutiepage before, our honest suggestion is: don't wait for a big occasion.

The platform is built for birthdays and anniversaries, but some of the nicest microsites we've seen weren't for a specific event at all. They were just a Tuesday.

A 'thank you for being a good friend' site in the middle of a regular week lands harder than the same gesture on a scheduled anniversary, because nobody's expecting it.

A 'you did the hard thing and I'm proud of you' site after a job interview, exam result, or difficult conversation often becomes the thing someone saves and rereads for years.

The templates are built for big moments, but they work just as well for small ones.

If you're not sure where to start, pick the smallest possible reason — you thought of someone, and you wanted to say so — and start there.

The platform will handle the rest.

A few prompts if you're stuck: who would you want to say thank you to that you've never actually thanked properly? Who's been good to you in a way you've taken for granted? Who is about to have a hard week?

Pick one of those. Make a small site. Send it. See what happens.

A sample walkthrough, start to finish

Let's do a hypothetical end-to-end example to make all of this concrete.

Imagine you want to make a birthday microsite for your best friend, whose birthday is next Saturday. You've got about an hour on a weekend afternoon.

You open cutiepage.com. You click on templates. You scroll through the grid and spend maybe three minutes looking.

There's a template called something like 'Scrapbook' that has a playful layout with room for multiple photos and short captions. That feels right for this friendship.

You click through. The template opens in a customiser. On the left is a set of fields: title, subtitle, a series of memory blocks, a cover photo, an accent colour.

You open a notes app in another tab. You write the title first: something simple, her name and the year. You write the subtitle: one line, affectionate, specific.

Then you open your camera roll and pick out six photos. Three from trips, two from regular hangouts, one old one from when you first met.

You paste each one into a memory block with a one-line caption describing what was happening in the photo. The captions are specific — not 'fun day', but 'the afternoon we accidentally ended up at that wedding'.

You preview. On your laptop first, then on your phone. You notice one photo is cropping awkwardly on mobile, so you go back and replace it with a more square version.

You preview again. It feels right.

You check out. Razorpay opens, you pay with UPI, the window closes. You're back on Cutiepage.

You pick a slug — some version of her name and a word only you two would recognise. You click publish.

Forty-five seconds later, the site is live. You have a URL.

You don't send it yet. You wait until Saturday morning. At 8 am, while she's having her first coffee, you send her the link with no other message.

Fifteen minutes later, she replies. What she replies with is not really something we can transcribe in a blog post. But it's the reason we built this.

Accessibility and inclusivity

We think a platform like this has a responsibility to work for everyone, so we've put real effort into accessibility.

All templates use sufficient colour contrast for text over backgrounds.

All interactive elements — buttons, toggles, galleries — are reachable by keyboard navigation as well as touch.

All images have alt text that you can customise, which makes the site meaningful to screen reader users.

Type sizes scale gracefully if the viewer has increased their system font.

Animations respect the 'prefers-reduced-motion' setting that many people enable at the OS level.

None of this is the kind of thing you have to think about when you're making a site. It's the platform's job to handle it, and we have.

If you ever find a template that falls short on accessibility, please tell us. We treat those reports as priority fixes.

Language support

Right now, the default language for the platform's own UI is English, but the content you write in the editor can be in any language.

Templates display Hindi, Bengali, Tamil, Marathi, and other Indic scripts correctly. We've tested emoji and punctuation across scripts.

If you're making a microsite for a parent or grandparent whose first language isn't English, we strongly recommend writing the message in their first language. The gesture lands much harder that way.

Mixed-language microsites also work — English prose with a line of Hindi at the end, or a Bengali title with English body text. The templates don't care. Write the way you actually speak.

When things go wrong

Occasionally something doesn't work. A photo fails to upload, a preview renders slowly, a payment hangs, a save gets stuck.

Our first line of defence is the editor's auto-save — most of your work is saved continuously, so a dropped connection or a browser refresh doesn't usually lose anything.

If you do lose progress, you can usually recover it by returning to the dashboard, where the in-progress draft will still be there.

If an upload fails, try again. Most upload failures are transient — network hiccups, cell tower handoffs, a brief Cloudinary blip.

If a payment fails, check your bank's transaction history before retrying. Sometimes the money has already left your account even though Razorpay reported a failure — in those cases the amount is auto-refunded within a few business days, and you can retry safely.

If a published site isn't loading for your recipient, the most common cause is a typo in the URL when copying the link. Double-check that you sent the exact URL we gave you.

For anything else, our contact page is the fastest route to a real human. Include your email, the slug of the site, and a short description of what went wrong. We'll get back to you.

What's coming next

Cutiepage is a young platform and we're adding things regularly.

A few things on the roadmap that we're excited about: more templates (we add one or two a month), better collaboration tools for families making a group microsite together, richer media support (video, audio clips, voice notes), and a scheduled-send feature so you can build a microsite now and have the link automatically sent to someone on a future date.

We prioritise based on what users ask for. If there's a feature you wish existed, please tell us. We read everything that comes in through the contact form, and the roadmap is genuinely shaped by those messages.

We also maintain a small set of 'things we will never do', which includes: no ads on microsites, no paid subscriptions, no locking existing free templates behind paywalls, no selling user data, and no making the product harder to use in exchange for metrics.

Those constraints matter to us. They're part of why the platform exists.

A few words about the people behind this

Cutiepage is a small team working out of India.

We care a lot about the product and we use it ourselves — most of us have sent microsites to our own partners, friends, and parents, and the feedback loop of being our own users has been one of the most useful things for the roadmap.

We answer support emails ourselves. There's no outsourced call centre. When you email us, you're emailing the people who built it.

If you want to reach out about anything — a bug, a feature idea, a weird edge case, a kind note about a microsite you made — we'd genuinely love to hear from you. The contact page has everything you need.

Where to go from here

The fastest way to see if Cutiepage is for you is to open the templates page and start customising one.

You don't have to pay anything to try it. You don't even have to publish it.

Just open a free template, type a few lines, upload a photo, and see how it feels. If it makes you smile, you'll know.

If you want to read more, we'll be publishing more guides on this blog: design tips for making your microsites feel more personal, write-ups of our favourite templates, occasional thoughts on the weird world of digital gifting, and tutorials for the less-obvious features.

You can bookmark this blog or check back every few weeks.

If you have a question we haven't answered here, our contact page is the best place to reach us. Real humans read the messages. We try to reply within a day, usually faster.

The best gifts aren't expensive. They're specific.

Closing thoughts

Cutiepage exists because we believe that the internet, for all its chaos, is still one of the most wonderful places to send a private, specific, kind gesture to another person.

A link opens in under a second. It works from anywhere. It costs almost nothing to send.

And when it's done well, it can feel as personal as a handwritten letter.

The platform is young, and we're adding things constantly — new templates, better editor tools, small touches that we notice while using it ourselves.

If you end up making a microsite and sending it to someone, we'd love to hear about the moment they opened it. Those stories are the reason we keep building.

Thanks for reading, and have fun with it.

That's really the whole thing.