Skip to content

Personal Components

Save and organize your custom Power Apps components in your own personal library.

Overview

In the product this library is called Custom YAML. You find it under the Custom Libraries tab in the library header (and under Your Libraries in the left sidebar). The page itself is headed Custom Components. It stores your own Power Apps YAML code alongside optional screenshots, so you have a personal library of reusable components that you can access anytime. The same tab also holds the Custom SVG Library at /library/svg-library, which keeps your own SVG icons in folders in the same way.

Available for: every paid plan except the old Components subscription. See pricing.

Why Use Personal Components?

Building Power Apps often means creating custom components that don't exist in the standard library. With Custom YAML, you can:

  • Save custom YAML code you've built
  • Store component screenshots for quick reference
  • Organize all your custom work in one place
  • Quickly find and reuse your own components across projects
  • Build your own component library tailored to your needs

Creating a Personal Component

Step 1: Open Custom YAML

  1. Go to the Component Library
  2. Open the Custom Libraries tab in the header and click the Custom YAML Library card (or click Custom YAML under Your Libraries in the left sidebar)
  3. You'll see your library at /library/customcomponents (empty if you haven't saved any component yet)

Step 2: Create New Component

Click the New Component button in the top right corner. This opens the Save New Component form.

Step 3: Fill in Component Details

Required Fields:

  • Title - Give your component a descriptive name (e.g., "Custom Login Form", "Dashboard Header")
  • YAML Code - Paste your Power Apps YAML code

Optional Fields:

  • Description - Add notes about what the component does or how to use it
  • Category - Pick a folder for the component, or create one from the form
  • Screenshot - Upload an image showing what the component looks like
    • Supported formats: PNG, JPEG, JPG, WEBP
    • Maximum size: 5MB
    • Tip: Take a screenshot of the component in Power Apps Studio for accurate reference

Step 4: Save Your Component

Click Save Component and your component will be added to your personal library.

Managing Your Components

Viewing Components

The Custom YAML page shows your folders as cards, then the folders shared with you, then the components that have no folder. Open a folder to see its components. Each component shows:

  • Component title
  • Description (if provided)
  • Screenshot preview (if uploaded)
  • YAML code tab for copying

Copying YAML Code

  1. Find the saved component card
  2. Click the Copy YAML button in the card header (it works from any tab), or open the YAML tab and click Copy
  3. Paste directly into Power Apps Studio

Your own components have no extra lock: as long as your account can open Custom YAML, you can copy every saved YAML.

Deleting Components

Single Component Deletion:

Hover over the component card and click the trash-can icon in its bottom left corner, then confirm in the browser dialog.

Bulk Deletion:

  1. Click the Select button (top right inside a folder, or next to the Uncategorized heading)
  2. Checkboxes appear next to each component
  3. Click the checkboxes of the components you want to delete
  4. A red bar appears above the components with a Delete Selected button (in the Uncategorized section the button reads Delete)
  5. Click it to delete (you'll see a confirmation dialog)
  6. Click Cancel to exit selection mode

In a folder that someone shared with you, the Select button and the icons on the cards only appear if you have Edit permission.

Best Practices

Naming Your Components

Use clear, descriptive names that help you quickly identify what each component does:

  • ✅ Good: "User Profile Card - Horizontal Layout"
  • ✅ Good: "Custom Search Bar with Filters"
  • ❌ Poor: "Component 1", "Test"

Adding Descriptions

Include helpful notes about:

  • What the component does
  • Where you use it in your apps
  • Any special configuration needed
  • Variables or data sources required

Taking Screenshots

For best results:

  • Use your operating system's screenshot tool (Power Apps Studio has no screenshot feature of its own)
  • Show the component in context when possible
  • Ensure the screenshot is clear and readable
  • Keep file sizes reasonable (under 1MB is ideal)

Organizing YAML Code

Before saving:

  • Format your YAML code properly
  • Test it in Power Apps first
  • Remove any sensitive data or test values
  • Add comments if helpful for future reference

Common Use Cases

Custom Form Layouts

Save specialized form layouts you use across multiple apps:

  • Multi-step wizards
  • Dynamic form sections
  • Custom validation patterns

Brand-Specific Components

Store components customized to your organization's branding:

  • Company headers and footers
  • Branded buttons and cards
  • Custom color schemes

Reusable Templates

Keep templates for recurring patterns:

  • Data table layouts
  • Dashboard widgets
  • Navigation patterns specific to your workflow

Experimental Components

Test new ideas and save working prototypes:

  • New interaction patterns
  • Custom animations
  • Innovative UI solutions

Tips & Tricks

Version History Is Automatic

Every time you edit a saved component, a new version is stored. Inside a folder, hover over the card and click the clock icon (its tooltip reads History (vN)) to open the Version History panel, where you can restore any earlier version with Restore. A restore brings back the title, description and YAML of that version and stores it as a new version, so nothing is overwritten; the screenshot is not part of the history. Only the owner of a component can open its history. Components in the Uncategorized section have no history button, so move them into a folder first. You do not need to put version numbers in the title.

Use consistent naming prefixes to group related components:

  • "Login - Form"
  • "Login - Header"
  • "Login - Footer"

Keep Notes in the Description

The version history records every change for you. Use the description field for notes that the history cannot hold, such as where you use the component and what it needs.

Regular Cleanup

Periodically review your personal library and delete components you no longer use to keep things organized.

Troubleshooting

Can't Access Personal Components

Solution: Custom YAML needs a paid plan other than the old Components subscription. If you are signed out, the page sends you to sign in. If you are signed in without such a plan, the page shows a locked "Custom Components" panel with an upgrade button that opens the plan options.

Upload Failed

If image upload fails:

  • Check file size (must be under 5MB)
  • Verify file format (PNG, JPEG, JPG, WEBP only)
  • Try compressing the image
  • Check your internet connection

Component Not Saving

Ensure both required fields are filled and within the limits:

  • Title cannot be empty and can be up to 200 characters long
  • YAML code cannot be empty and can be up to about 1 MB of text (1,048,576 characters)
  • The description can be up to 10,000 characters long

Can't See My Components

Try refreshing the page. If components still don't appear, check:

  • You're logged in to the correct account
  • Your account has a paid plan other than the old Components subscription

Categories

The product calls these folders. Organize your components into folders for better management.

Creating Categories

  1. Go to Custom YAML
  2. Click New Folder
  3. Enter a name of up to 50 characters in the browser prompt (e.g., "Login Screens", "Dashboard Widgets")
  4. Confirm with OK

Folders can hold subfolders, one level deep: open a folder and click New Subfolder. Two folders at the same level cannot have the same name.

Renaming and Deleting Categories

Open the folder and click the three-dot button in the top right. The menu offers Share Category, Rename Category and Delete Category (only the owner of the folder sees it). Deleting a folder also deletes its subfolders. The components inside are not deleted; they move to the Uncategorized section.

Moving Components to Categories

When saving a new component, pick a folder in the Category (optional) field of the form. To move an existing component, hover over its card, click the Edit icon in the bottom left corner and change the category, then click Update Component. The field lists your top-level folders; to put a component into a subfolder, open the subfolder and click New Component there.

Uncategorized Components

Components without a folder appear in the "Uncategorized" section. You can organize them later.

Sharing Categories with Team Members

Share your folders with colleagues so they can access your custom components.

How to Share

  1. Go to Custom YAML
  2. Find the folder you want to share
  3. Hover over the folder card and click the share icon in its top left corner (only the owner sees it), or open the folder and choose Share Category in the three-dot menu
  4. Enter the email address of your colleague
  5. Choose permission level:
    • View - They can see and copy components
    • Edit - They can also add/modify components
  6. Click "Share"

An email invitation is sent every time. The share is stored by email address and linked to the PowerLibs account with that address, where the folder then appears in the "Shared with me" section. The recipient also needs a paid plan other than the old Components subscription to open the library. You can send up to 20 invitations per hour.

Permission Levels

PermissionCan ViewCan CopyCan EditCan Delete
View✓✓✗✗
Edit✓✓✓✓

Shared Categories Section

When someone shares a folder with you, it appears in a separate "Shared with me" section on the Custom YAML page. You'll see:

  • Folder name
  • Owner's email
  • Your permission level
  • Component count

Managing Shares

Viewing who has access: Click the Share icon on a folder you own to see all current shares.

Changing permissions: In the share dialog, change the permission dropdown next to the person's email. The change is saved at once.

Removing access: Click the trash-can icon next to a person's email in the "People with access" list of the share dialog.

Sharing Best Practices

  • Use View for reference libraries - When you want others to see but not modify
  • Use Edit for team collaboration - When building components together
  • Share folders, not individual components - It's more organized
  • Name folders clearly - "HR Portal Components" is better than "My Stuff"

Sharing a Component with the Community

The Community page (Shared Components in the left sidebar) shows components that makers have published. You can publish one of yours in two ways:

  • On the Community page, click Submit Component. Fill in the same form as above; here the screenshot is required. After you save, the Share to Community dialog opens. The component is also saved in your Custom YAML library.
  • On the Custom YAML page, hover over a component in the Uncategorized section and click the globe icon (Share to Community).

In the dialog, enter a Display Name of up to 60 characters (it is shown as the author) or switch on Post anonymously, then click Publish. A component without a screenshot cannot be published: add one first. Names that read like PowerLibs itself, such as Support or Admin, are refused.

On a published component the globe icon is green. Click it and confirm with Remove to take the component off the Community page; you can share it again later. Publishing needs an account that can use Custom YAML.

Access Requirements

Who Can Use Personal Components: every account with a paid plan other than the old Components subscription. When a plan ends, your saved components stay in the account but cannot be opened until a plan is active again.

What's Included:

  • Image uploads up to 5MB per component
  • Create, view, edit and delete components, with a version history you can restore from
  • Instant YAML code access
  • Folders and subfolders
  • Sharing with team members

Next Steps


Need help? Use the Ideas + Bugs page to report issues or request features.

Personal Components | PowerLibs